fix(gateway): handle invalid project names in ScopedUser #1396
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 of change
Fixes endpoints with ScopedUser that are called with an invalid project name. Returns proper project name error instead of panic. The error is also properly logged instead of a panic printout.
Bonus change: red 🟥
How has this been tested? (if applicable)
Before:
After:
Both of these give 400 instead of no response:
curl -v -H 'Authorization: Bearer dh9z58jttoes3qvt' localhost:8001/projects/äö
curl -v -H 'Authorization: Bearer dh9z58jttoes3qvt' localhost:8001/projects/äö/services/äö