-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Refactor of item-level permission to be more intuitive #3760
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed now unused JS entity-permissions compontent. Updated existing permissions-table compontent to newer format. Removed now unused translation string.
Nothing on back-end logic done to hook this new option up. Addition of permissions for role_id=0 works out of the box, but active "everyone else" permissions, with no priviliges, is currently not working. Needs change of permission gen logic also.
Added test to cover.
Simplifies structure and limits content count, while allowing direct mapping of new UI intent, where we may have entries with no permissions. Not yet updated app logic to suit. Tested via migrating and rolling-back, then comparing export data, across a set of custom permission entries.
Also introduced helpers for getting entities by slugs since we do it in so many places.
Also updates show roles on permission view to just those with permissions applied. Fixes rounded borders for lone permission rows. Moves "Everyone Else" handling from role to new class.
Also removed now unused view.
- Fixed inheriting control for new system. - Tested copying shelf permissions to books. - Added additional handling for inheriting scenario identification.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #410
Also makes the item permissions view much more mobile responsive.
Todo
restricted=0
. DOCUMENT.restricted=1
item entries with new "Other Roles" option with no permissions.restricted
entity field.Handle/warn/document removal ofNot part of API data AFAICT.restricted
field in API data (If exists).Docs Updates