Ensure skip_defaults
doesn't cause extra fields to be serialized
#485
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.
Currently, if
skip_defaults
is true, the secure cloned field is not used when serializing the response. This can lead to extra information leaking out if theresponse_model
differs in type from the returned model.This pull request fixes this bug, and updates the relevant unit test to check for it.
(The bug was introduced in #422 -- sorry about that!)
I believe this pull request also improves performance in the case where
skip_defaults
isTrue
, as the response will now only be validated once in theserialize_response
call, instead of twice.