[Feature/966] Account Permissions Redesign #151
Merged
Conversation
This file contains 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
Along with the updated name, ported over common user checks into the service and updated the logic to work with the new permissions system. Awaiting new API endpoint to retrieve the auth user's permissions before continuing.
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.
What Does This Do?
Updates the website to utilize the new permission system that will be deployed on the next release. Permissions are going from a role-based system to a hybrid user & role system where the site can adequately apply and remove permissions to various features to individual users.
How is it Done?
Updated the existing user cookie service to handle a new private parameter to store all of the permissions. Permissions list is refetched on any authentication guard (to verify with the server that the user does hold those permissions) and on first load (as the permissions list the user has is not cached after fetching).
Related Tickets and Issues
Ticket: Internal#966
This is also paired with a pull request for the API, denoted using the same ticket number in the title.