Set up permissions for verify and unverify and UI for unverify #34
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.
Description
Previously, any user could verify/unverify a post which would make the feature useless since a student could just verify their own post. This PR would ensure that only certain individuals are able to verify the post and that students would be unable to do so. This goes beyond just frontend logic but also protects backend API calls so that students would not be able to verify their own post by sending a CURL request.
This PR does the following:
With this PR, the verify message feature can now allow only admins/mods to verify a message and the change will be propagated in both the frontend and backend (saved as a variable in the post struct). Resolves #21 and #33.
Testing
Automated unit tests for permissions have been added and lint checks are also tested.