-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add linter to check for correct navigation permissions #97
Comments
Good thought, though also I'd really like to enhance the nav menu API in core at some point so that the common case can implicitly derive the correct permissions without needing so much duplication of information. |
Let's not go down the depth of trying to introspect the router. Instead, let's just duck-type the link and permissions to ensure they follow the conventions ( |
Environment
Proposed Functionality
Ensure that if permissions are used in NavMenu items that they match the model being used in the linked view. For example, if you are adding a navigation menu item to the
plugins:example_app:examplemodel_list
view, the permission should be forexample_app.view_examplemodel
. See theNavigation Menu
docs for more information.Use Case
The text was updated successfully, but these errors were encountered: