-
Notifications
You must be signed in to change notification settings - Fork 3
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
PS-160: require superuser or official for event put delete #165
base: main
Are you sure you want to change the base?
PS-160: require superuser or official for event put delete #165
Conversation
Need to add cases for patching (contractors should be allowed to PATCH event state). |
dcd2519
to
7372ce3
Compare
PUISTOTALKOOT-API branch is deployed to platta: https://puistotalkoot-pr165.api.dev.hel.ninja 🚀🚀🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, the use of generic permission logic is pleasing to the eye.
ReadOnly, IsOfficial and IsSuperUser Refs: PS-160, PS-159
BREAKING CHANGE: event view responds with 403/401 instead of 404 if the request has insufficient permissions or tries to access an endpoint that requires authentication BREAKING CHANGE: event update & delete requires superuser or official status (i.e. contractor cannot modify or delete their own events anymore) Refs: PS-160, PS-159
Refs: PS-160, PS-159
Refs: PS-160, PS-159
7372ce3
to
c871710
Compare
Quality Gate passedIssues Measures |
PUISTOTALKOOT-API branch is deployed to platta: https://puistotalkoot-pr165.api.dev.hel.ninja 🚀🚀🚀 |
Require superuser or official status for event view put/delete. This itself is a breaking change, but this also changes the response code for unauthenticated requests/requests with insufficient permissions to 401/403 (from 404).
Also refactor the tests a bit.