fix: stop leaking User into API handlers unless authorized #10172
Conversation
This file contains hidden or 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
This was referenced Oct 10, 2023
|
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
johnstcn
approved these changes
Oct 10, 2023
Base automatically changed from
10-10-chore_refactor_conversion_to_accept_ownerName
to
main
October 10, 2023 12:55
b39a6a9 to
3cabbf6
Compare
3cabbf6 to
43e4f42
Compare
Merge Activity
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes an issue where we extracted the
{user}parameter from the URL and added it to the API Handler context regardless of whether the caller had permission to read the User.