fix(HTTP): Adjust JSONResponse data type #50035
Merged
Conversation
This file contains 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
Signed-off-by: provokateurin <kate@provokateurin.de>
|
/backport to stable30 |
|
/backport to stable29 |
|
/backport to stable28 |
|
Backport to stable28 is only for OpenAPI, even though it is already EOL. |
4 tasks
come-nc
approved these changes
Jan 6, 2025
nickvergessen
approved these changes
Jan 7, 2025
This was referenced Jan 7, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Just saw an app return a literal string value in a JSONResponse which is totally valid.
I adjusted the types to match https://json-schema.org/understanding-json-schema/reference/type, as
objectalso wasn't correct (and neither ismixed).Checklist