fix: Remove multiselect until errors fixed #2530
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
|
Thank you for following the naming conventions for pull request titles! 🙏 |
MichaelUnkey
requested review from
perkinsjr,
chronark and
mcstepp
as code owners
📝 Walkthrough📝 Walkthrough📝 Walkthrough📝 WalkthroughWalkthroughThe changes in this pull request modify the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
apps/dashboard/app/(app)/authorization/roles/create-new-role.tsx (1)
Incomplete Removal of
permissionOptionsReferencesSeveral references to
permissionOptionsstill exist withincreate-new-role.tsx, which may lead to potential bugs or inconsistent behavior:
permissionOptions: zpermissionIds: values.permissionOptions?.map((o) => o.value),name="permissionOptions"return form.setValue("permissionOptions", cb(field.value ?? []));Recommended Actions:
- Complete Removal: Ensure all instances of
permissionOptionsare removed if the feature is no longer needed.- Proper Handling: If
permissionOptionsis intended to be temporarily disabled, implement proper error handling or feature flags to manage its state without leaving residual references.🔗 Analysis chain
Line range hint
145-175: Temporary fix applied, follow-up requiredThe temporary removal of the permissions selection aligns with the PR objectives to address issues with the multi-select functionality. However, this change has several implications:
- User Experience: Users can no longer select permissions during role creation, which may impact their workflow.
- Functionality: The ability to assign permissions to roles at creation time is now limited, potentially affecting the completeness of role definitions.
- Technical Debt: Commenting out code instead of proper error handling or feature flagging introduces technical debt.
To ensure this change meets the PR objectives and doesn't introduce new issues:
Would you like assistance in creating a follow-up task to properly implement the permissions selection feature?
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Verify that roles can still be created and that there are no lingering references to the commented-out functionality # Check for any remaining references to permissionOptions in the file echo "Checking for remaining references to permissionOptions:" rg 'permissionOptions' apps/dashboard/app/\(app\)/authorization/roles/create-new-role.tsx # Verify that the role creation mutation is still intact echo "Verifying role creation mutation:" rg 'createRole.mutate' apps/dashboard/app/\(app\)/authorization/roles/create-new-role.tsx # Check for any TODO or FIXME comments related to this change echo "Checking for TODO or FIXME comments:" rg -i 'TODO|FIXME' apps/dashboard/app/\(app\)/authorization/roles/create-new-role.tsxLength of output: 796
Script:
#!/bin/bash # Search for all occurrences of 'permissionOptions' in the codebase to identify dependencies echo "Searching for all references to 'permissionOptions' in the repository:" rg 'permissionOptions'Length of output: 663
|
@MichaelUnkey please fix the lint issue |
What does this PR do?
Can get the permissions to show. No selection can be made and still shows some errors.
For now I removed the multi select, After role creation the next page allows you to select permissions anyway. For now it will at least stop errors.
Fixes # (issue)
eng-1418
Type of change
How should this be tested?
Role can still be created.
Checklist
Required
pnpm buildpnpm fmtconsole.logsgit pull origin mainAppreciated
Summary by CodeRabbit
Summary by CodeRabbit
Bug Fixes
Chores