Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve access control invites error handling to show single snackbar #469

Merged
merged 3 commits into from
Dec 18, 2024

Conversation

rushil95
Copy link
Contributor

@rushil95 rushil95 commented Dec 16, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced user invitation process with improved error handling and feedback.
    • Added a parameter to suppress global error notifications during user invitations.
  • Bug Fixes

    • Improved error messaging to provide more detailed feedback on failures.
  • Chores

    • Normalized role types to lowercase for consistency during form submissions.
    • Ensured structured cloning of values before submission to preserve original data.

Copy link
Contributor

coderabbitai bot commented Dec 16, 2024

Walkthrough

The pull request introduces modifications to the user invitation process in the AccessControl component and the inviteSubscriptionUser function. The changes primarily focus on enhancing error handling and adding a new parameter to suppress global error notifications. The createUserInvitesMutation function now includes explicit success and error callbacks, and the inviteSubscriptionUser function now accepts an optional parameter to control error snackbar display.

Changes

File Change Summary
pages/access/[serviceId]/[environmentId]/access-control.js - Updated createUserInvitesMutation with explicit onSuccess and onError callbacks
- Added structured cloning of form values
- Normalized role types to lowercase
- Modified function to pass an additional parameter to inviteSubscriptionUser
src/api/users.js - Updated inviteSubscriptionUser function signature to include suppressErrorSnackbar
- Added conditional ignoreGlobalErrorSnack option in axios request configuration

Possibly related PRs

Suggested reviewers

  • Nithishprem

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc2657b and 2b65735.

📒 Files selected for processing (1)
  • pages/access/[serviceId]/[environmentId]/access-control.js (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/access/[serviceId]/[environmentId]/access-control.js

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
src/api/users.js (1)

11-21: LGTM! Consider adding JSDoc documentation.

The changes to add suppressErrorSnackbar parameter look good and align well with the PR objective. The implementation correctly uses axios configuration to control error handling behavior.

Consider adding JSDoc documentation to clarify the parameter's purpose:

+/**
+ * Invites a user to a subscription
+ * @param {string} subscriptionId - The ID of the subscription
+ * @param {Object} payload - The invitation payload
+ * @param {boolean} [suppressErrorSnackbar=false] - When true, suppresses global error notifications
+ * @returns {Promise} Axios promise
+ */
export const inviteSubscriptionUser = (
  subscriptionId,
  payload,
  suppressErrorSnackbar = false
) =>
pages/access/[serviceId]/[environmentId]/access-control.js (2)

129-169: LGTM! Consider improving error message formatting.

The enhanced error handling looks good:

  • Suppressing global errors prevents duplicate notifications
  • Success and error callbacks are well-defined
  • Backend error details help users understand failures better

Consider extracting the error message to a separate component or using template literals for better readability:

-        snackbar.showError(
-          <>
-            Some invites were not sent. Please retry
-            {backendErrorMessage ? (
-              <>
-                <br />
-                Error details: {backendErrorMessage}{" "}
-              </>
-            ) : (
-              ""
-            )}
-          </>
-        );
+        const errorMessage = backendErrorMessage
+          ? `Some invites were not sent. Please retry\nError details: ${backendErrorMessage}`
+          : "Some invites were not sent. Please retry";
+        snackbar.showError(errorMessage);

Line range hint 214-227: Consider extracting role type normalization logic.

The form submission changes look good, but the role type normalization logic could be more maintainable.

Consider extracting the role type normalization to a utility function:

+const normalizeRoleType = (roleType) => {
+  const roleMap = {
+    'Editor': 'editor',
+    'Reader': 'reader'
+  };
+  return roleMap[roleType] || roleType;
+};

 onSubmit: (values) => {
   const valuesToBeSubmitted = structuredClone(values);
-  for (let i = 0; i < valuesToBeSubmitted?.userInvite?.length; i++) {
-    if (valuesToBeSubmitted.userInvite[i]["roleType"] === "Editor") {
-      valuesToBeSubmitted.userInvite[i]["roleType"] = "editor";
-    }
-    if (valuesToBeSubmitted.userInvite[i]["roleType"] === "Reader") {
-      valuesToBeSubmitted.userInvite[i]["roleType"] = "reader";
-    }
-  }
+  valuesToBeSubmitted.userInvite = valuesToBeSubmitted.userInvite.map(invite => ({
+    ...invite,
+    roleType: normalizeRoleType(invite.roleType)
+  }));
   createUserInvitesMutation.mutate(valuesToBeSubmitted);
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c613b7c and cc2657b.

📒 Files selected for processing (2)
  • pages/access/[serviceId]/[environmentId]/access-control.js (1 hunks)
  • src/api/users.js (1 hunks)

@rushil95 rushil95 merged commit 5954ede into master Dec 18, 2024
6 checks passed
@rushil95 rushil95 deleted the access-control-error-handling branch December 18, 2024 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants