use type() in int validator #264
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.
Change Summary
This fixes an issue I would not expect where if you pass
True | Falseto and field typed withintyou'll get theboolvalue inside your object. I would expect to getintvalues1 | 0This is because in python aboolis actually a subclass ofintsoisinstance(True, int)returnsTrue. Usingtype(True) is intreturnsFalseand will therefore causeTrueto be cast to anintwhich I think falls in line with how the other validators work.Related issue number
I didn't see any.
Performance Changes
pydantic cares about performance, if there's any risk performance changed on this PR,
please run
make benchmark-pydanticbefore and after the change:Checklist
HISTORY.rsthas been updated#<number>@whatever