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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⬆️Pydantic V2: Diverse fixes after merges from master #6627
⬆️Pydantic V2: Diverse fixes after merges from master #6627
Changes from 14 commits
a945c6d
8ab4371
64cf5d0
4408874
67254ed
7cbf1e6
638ded4
b2074f7
87e7094
3baa3f8
b74a6cf
17cbd4f
0f5cd62
eca9d9a
6b18099
cf55b7b
6855b2e
a431816
1fe02f3
e8d7414
670200b
c0f2d97
c814e9b
e3b7ccc
2e20fb8
367c12b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if the rest noticed this. perhaps add it in the description of the PR ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why you add
Field
when we only look for the default?THOUGHT: I wonder if we should start using
Annotated
instead of abusing of the "exception to the rule" of adding a default (i.e.Field
) that is not an instance of the type annotated. It kind of similar to the story withFieldRequired
that exploited an edge case that now was removed.Perhaps is an unnecessary burden ... it does not really pay off!