Add comments on risky permissions#1468
Conversation
Some permissions in the Backend and CMS are expected to be given only to trusted users, as they grant access to features of the CMS that can negatively manipulate the experience of other users or grant themselves more access than intended. We now make this explicit by providing hints about these permissions.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds permission comment metadata across backend, CMS, and system modules; updates permission editor to show comments as a tooltip icon; adds translations for the new comments; clarifies the allow_unsafe_markdown label; and adds Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment Tip You can disable the changed files summary in the walkthrough.Disable the |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@modules/backend/formwidgets/permissioneditor/partials/_permissioneditor.php`:
- Around line 58-60: The icon-only span showing $permission->comment is not
keyboard/screen-reader accessible; make it focusable and expose the comment text
to assistive tech by updating the span with tabindex="0" and an accessible name
(either aria-label="<?= e(trans($permission->comment)) ?>" or aria-describedby
pointing to a visually-hidden element containing <?=
e(trans($permission->comment)) ?>), keep the existing classes
(wn-icon-circle-info/text-info) and tooltip attributes, and ensure the
visually-hidden text (e.g., class="sr-only" or "visually-hidden") is present so
screen readers and keyboard users can discover the permission risk.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7d56382b-bc5d-4ef4-bb5b-e405b7f33db1
📒 Files selected for processing (7)
.gitignoremodules/backend/ServiceProvider.phpmodules/backend/formwidgets/permissioneditor/partials/_permissioneditor.phpmodules/backend/lang/en/lang.phpmodules/cms/ServiceProvider.phpmodules/cms/lang/en/lang.phpmodules/system/lang/en/lang.php
modules/backend/formwidgets/permissioneditor/partials/_permissioneditor.php
Show resolved
Hide resolved
…ioneditor.php Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
To assist admins when assigning permissions to users, I have added comments to permissions that should only be given to trusted users. These permissions, if given to untrusted users, may pose a security risk due to being able to negatively manipulate the experience of other users, or could be potentially used to grant themselves more access than intended.
Summary by CodeRabbit
New Features
Documentation