-
Notifications
You must be signed in to change notification settings - Fork 429
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
fix: Tighten ACL for user routes #2929
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Quick typing suggestions, otherwise LGTM 👍
Uffizzi Preview |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2929 +/- ##
==========================================
+ Coverage 95.61% 95.62% +0.01%
==========================================
Files 1011 1011
Lines 29023 29038 +15
==========================================
+ Hits 27749 27767 +18
+ Misses 1274 1271 -3
☔ View full report in Codecov by Sentry. |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingChanges
I found these routes were wide open while working on a separate PR that had an endpoint with the same issue. The changes simply fix the order of the decorators and stop the incorrect instantiation of the permission classes into instances.
How did you test this code?
I wrote two tests that verified that the code was broken then watched them pass.