Skip to content

feat: enhance user management table with user context and selection logic #1486

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

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

chiol
Copy link
Contributor

@chiol chiol commented Apr 22, 2025

Summary by CodeRabbit

  • New Features

    • Added a "Me" badge next to the logged-in user's email in the user management table.
    • Prevented users from selecting or deleting their own account in the user management interface.
  • Bug Fixes

    • Improved filtering to exclude users of type 'SUPER' from project member lists.
  • UI Improvements

    • Enhanced table selection logic for clearer feedback when selecting multiple users.

Copy link

coderabbitai bot commented Apr 22, 2025

Walkthrough

The changes introduce new restrictions and UI feedback in the user management features of the application. On the backend, the member service now excludes users with the type 'SUPER' when fetching project members. On the frontend, the user management table and its columns are updated to prevent the currently logged-in user from selecting or deleting their own user entry. Additionally, a "Me" badge is displayed next to the logged-in user's email in the table, and some minor logic improvements and logging were added to the table's selection handling.

Changes

File(s) Change Summary
apps/api/src/domains/admin/project/member/member.service.ts Updated the findAll method in MemberService to exclude members whose associated user's type is 'SUPER' by adding a filter to the query.
apps/web/src/entities/user/ui/user-management-table.ui.tsx Prevented the logged-in user from selecting or deleting their own entry in the user management table by disabling row selection and the delete button for their row; used useUserStore to access the current user's email.
apps/web/src/entities/user/user-columns.tsx Added use of useUserStore to show a "Me" badge next to the logged-in user's email; refined the checkbox header logic and added logging to the selection handler; simplified some column logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UserManagementTable
    participant useUserStore

    User->>UserManagementTable: Render table
    UserManagementTable->>useUserStore: Get current user's email
    UserManagementTable-->>User: Display table
    alt Row is current user
        UserManagementTable-->>User: Disable selection and delete for own row
        UserManagementTable-->>User: Show "Me" badge next to email
    else Other users
        UserManagementTable-->>User: Enable selection and delete
    end
Loading
sequenceDiagram
    participant MemberService
    participant Database

    MemberService->>Database: Query members by project ID
    Note right of MemberService: Excludes users where type = 'SUPER'
    Database-->>MemberService: Return filtered members
Loading
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @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

@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 (1)
apps/web/src/entities/user/user-columns.tsx (1)

35-43: Remove debugging console.log statements.

The console.log statements appear to be debugging code that should be removed before merging to production.

        indeterminate={
          table.getIsSomeRowsSelected() && !table.getIsAllRowsSelected()
        }
        onCheckedChange={(checked) => {
-          console.log('checked: ', checked);
-          console.log(table.getIsAllRowsSelected());
          table.toggleAllRowsSelected(checked);
        }}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 72ee586 and a68232c.

📒 Files selected for processing (3)
  • apps/api/src/domains/admin/project/member/member.service.ts (1 hunks)
  • apps/web/src/entities/user/ui/user-management-table.ui.tsx (4 hunks)
  • apps/web/src/entities/user/user-columns.tsx (4 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
apps/web/src/entities/user/user-columns.tsx (1)
apps/web/src/entities/user/user.model.ts (1)
  • useUserStore (44-98)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: integration-test
🔇 Additional comments (7)
apps/api/src/domains/admin/project/member/member.service.ts (1)

108-108: Filter implementation for excluding SUPER type users looks good.

The addition of this filter ensures that users with the 'SUPER' type are not included in the project member results, aligning with the security principle of restricting visibility of privileged accounts in regular user management interfaces.

apps/web/src/entities/user/ui/user-management-table.ui.tsx (3)

43-43: Good addition of useUserStore for user context.

The import and use of the user store provides necessary context for implementing the user-based restrictions in the table.

Also applies to: 54-54


93-93: Security improvement for preventing self-selection.

This is a good safety measure that prevents users from selecting their own record, which could lead to accidental self-deletion.


187-187: Security enhancement for preventing self-deletion.

Disabling the delete button when editing the current user's record adds an additional layer of protection against accidental account deletion.

apps/web/src/entities/user/user-columns.tsx (3)

24-24: Good addition of useUserStore for identifying the current user.

This import enables the "Me" badge feature to highlight the current user's record in the table.


59-68: Good implementation of the "Me" badge for self-identification.

Adding a visual indicator next to the current user's email helps with identification in the table. It also visually reinforces which user record cannot be selected or deleted based on the restrictions added in the table component.


99-101: Good code simplification for type column.

The refactoring of these methods to use arrow function shorthand improves code readability without changing functionality.

@chiol chiol requested a review from jihun April 22, 2025 08:34
@chiol chiol self-assigned this Apr 22, 2025
@chiol chiol marked this pull request as draft April 23, 2025 04:55
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