Repository navigation
Use validation_alias for embedded bodies - #16
Merged
Merged
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
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.
On non-streaming routes,
Body(embed=True, validation_alias=...)was ignored: the embedded body key wasaliasor the parameter name, unlike plain FastAPI, where the key is a stringvalidation_alias. A body sent undervalidation_aliaswas rejected, or replaced by the default when the body was optional. Now thisvalidation_aliasis the key in the request, in error locations and in the OpenAPI schema. This also corrects the request schema of streaming routes, where the request key was already right.As in FastAPI,
AliasChoicesandAliasPathdo not change the key read from an embedded body.