Fix incorrect subclass check for secretstr #6730
Merged
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 subclasses of SecretStr fail to evaluate
self.field_type is SecretStr
and default tobytes_type
. This is not how it should go as the subclass explicitly subclasses the SecretStr type.This fix tests if the type is of SecretStr with
issubclass
which states:Which makes is backwards compatible for the actual SecretStr as well.
Change Summary
Allow pydantic scheme creation to work with subclasses of
SecretStr
Related issue number
fix #6729
Checklist
Selected Reviewer: @davidhewitt