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

[WEB-2606] fix: project members shouldn't be able to change others roles #5802

Open
wants to merge 2 commits into
base: preview
Choose a base branch
from

Conversation

sharma01ketan
Copy link
Collaborator

@sharma01ketan sharma01ketan commented Oct 11, 2024

[WEB-2606]

This PR aims to fix the bug where a Project Member is able to edit the details in the frontend of other Project Members in the Project Settings

Previous State:

Screen.Recording.2024-10-09.at.4.18.21.PM.mov

Current State:

No Dropdown appears on other Project Members name.

Screenshot 2024-10-09 at 4 19 28 PM

Summary by CodeRabbit

  • New Features

    • Enhanced role management for project members, allowing for more nuanced control over role editability based on user membership status.
    • Introduced a method to retrieve specific project member details.
  • Bug Fixes

    • Improved logic for determining non-editable roles based on current user membership in the project.

@sharma01ketan sharma01ketan added 🐛bug Something isn't working 🌐frontend labels Oct 11, 2024
@sharma01ketan sharma01ketan added this to the v0.24.0 milestone Oct 11, 2024
@sharma01ketan sharma01ketan self-assigned this Oct 11, 2024
Copy link
Contributor

coderabbitai bot commented Oct 11, 2024

Walkthrough

The changes in this pull request focus on the AccountTypeColumn component within the member-columns.tsx file. The modifications include the addition of the getProjectMemberDetails method to the useMember hook, enhancing the component's ability to determine if the current user is a project member. The logic for non-editable roles is refined with the introduction of the isCurrentUserProjectMember variable, which influences role editing capabilities based on user membership status. The overall structure of the component remains intact, ensuring the rendering logic for the role selection interface continues to function properly.

Changes

File Path Change Summary
web/core/components/project/settings/member-columns.tsx Updated AccountTypeColumn to include getProjectMemberDetails in the useMember hook and refined role editability logic with isCurrentUserProjectMember.

Possibly related PRs

Suggested reviewers

  • sriramveeraghanta
  • SatishGandham
  • gurusainath

Poem

🐰 In the meadow where members play,
New details bloom, brightening the day.
Roles now shift with a gentle glance,
Users dance in a membership trance.
With edits refined, we hop with glee,
A project united, as it should be! 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 793c39d and 996e5e8.

📒 Files selected for processing (1)
  • web/core/components/project/settings/member-columns.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • web/core/components/project/settings/member-columns.tsx

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 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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3011ef9 and 793c39d.

📒 Files selected for processing (1)
  • web/core/components/project/settings/member-columns.tsx (2 hunks)
🧰 Additional context used
🔇 Additional comments (1)
web/core/components/project/settings/member-columns.tsx (1)

93-93: Proper inclusion of getProjectMemberDetails

The addition of getProjectMemberDetails allows for checking project member details, which is necessary for role verification.

@@ -101,7 +101,9 @@ export const AccountTypeColumn: React.FC<AccountTypeProps> = observer((props) =>
const isWorkspaceMember = [EUserPermissions.MEMBER].includes(
Number(getWorkspaceMemberDetails(rowData.member.id)?.role) ?? EUserPermissions.GUEST
);
const isRoleNonEditable = isCurrentUser || (isProjectAdminOrGuest && !isWorkspaceMember);
const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role == EUserPermissions.MEMBER;
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Ensure currentUser is defined to prevent potential errors

When currentUser is undefined, currentUser?.id ?? "" results in an empty string. Calling getProjectMemberDetails with an empty string may lead to unexpected behavior or errors. Consider checking if currentUser is defined before calling getProjectMemberDetails.

Apply this diff to address the issue:

-const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role == EUserPermissions.MEMBER;
+const isCurrentUserProjectMember = currentUser
+  ? getProjectMemberDetails(currentUser.id)?.role === EUserPermissions.MEMBER
+  : false;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role == EUserPermissions.MEMBER;
const isCurrentUserProjectMember = currentUser
? getProjectMemberDetails(currentUser.id)?.role === EUserPermissions.MEMBER
: false;

🛠️ Refactor suggestion

Use strict equality operator (===) for role comparison

It's recommended to use the strict equality operator === instead of == to prevent unintended type coercion during comparison.

Apply this diff:

-const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role == EUserPermissions.MEMBER;
+const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role === EUserPermissions.MEMBER;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role == EUserPermissions.MEMBER;
const isCurrentUserProjectMember = getProjectMemberDetails(currentUser?.id ?? "")?.role === EUserPermissions.MEMBER;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working 🌐frontend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants