add permissions for routes in frontend #637
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
magsyg
force-pushed
the
feature/permissions
branch
from
a702886
to
f99c344
Compare
emilte
reviewed
Jul 6, 2023
emilte
reviewed
Jul 6, 2023
emilte
reviewed
Jul 6, 2023
emilte
reviewed
Jul 6, 2023
emilte
reviewed
Jul 6, 2023
|
La til slik at dersom man er logget inn så blir man redirected fra loginpage til homescreen, eller prøvd admin page dersom man prøvde seg dit |
added 2 commits
July 10, 2023 16:42
emilte
approved these changes
Jul 11, 2023
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.
Added a ProtectedRoute, which takes in permissions, and returns the correct route if correct, if false it redirects to home or future 403 page.
Will add for rest of the admin routes, now only tested on gangs, at it seems to work
Still has a bug where it does not accept manual routes, because of useAuthContext takes time to load.
Should find a fix in routes for loading User