Only fetch __pydantic_core_schema__
from the current class during schema generation
#10518
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.
In some cases, the core schema of a class is not the right one:
Until now, we had the
existing_schema.get('cls', None) is obj
check to avoid incorrectly using the core schema in this case. However, this doesn't work if the core schema is of typedefinitions
, in which caseexisting_schema.get('cls', None) is obj
isFalse
even though it is the correct schema. This was found during the ns refactor.Change Summary
Related issue number
Checklist