Replacing encode_default instance check with strict type check #3197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please review :) |
|
Please review. 🙂 |
joaommartins
deleted the
bugfix/make-schema-encode_default-parse-intenum-correctly
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Modifies the schema default resolution of
encode_defaultto resolve IntEnum correctly by introducing a strict type check against primitives. IntEnum defaults are resolved bypydantic_encodercorrectly in the same way Enum defaults are resolved.Related issue number
Closes #3190.
Checklist
changes/<pull request or issue id>-<github username>.mdfile added describing change(see changes/README.md for details)