Fix schema for timedelta as number, instead of str #325
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
Currently, the generated schema for
datetime.timedelta
is asstring
.But by default, Pydantic will convert it to a
float
with the difference in seconds.(Bug created by me in the JSON Schema compatibility PR).
This PR fixes that and makes the schema for
timedelta
be anumber
by default, which corresponds to the actual behavior.Related issue number
I didn't create one.
Performance Changes
pydantic cares about performance, if there's any risk performance changed on this PR,
please run
make benchmark-pydantic
before and after the change:Checklist
HISTORY.rst
has been updated#<number>
@whatever