Repository navigation
fix: python schema optional fields are not marked required - #462
Open
fernandezcuesta wants to merge 1 commit into
Open
fernandezcuesta wants to merge 1 commit into
fernandezcuesta wants to merge 1 commit into
Conversation
Signed-off-by: Jesús Fernández <7312236+fernandezcuesta@users.noreply.github.com>
fernandezcuesta
marked this pull request as ready for review
October 28, 2026 16:00
fernandezcuesta
requested review from
a team,
jcogilvie and
tampakrap
as code owners
October 28, 2026 16:00
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 53 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or 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
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.
Description of your changes
Fixes #394
Pass
--use-default-kwargtodatamodel-code-generatorso it writes field defaults with thedefault=keyword, as inField(default=None, alias='continue').Pyright and Pylance read defaults only from that keyword, so they reported these fields as required. They now treat them as optional.
Reproduced with the pinned
datamodel-code-generator:0.59.0image and the CLI's arguments, on a minimal OpenAPI spec with the two cases from #394 (a field renamed from a Python keyword, and an object field with a{}default).Generated models, without and with
--use-default-kwarg:Type-checking this script with pyright 1.1.406:
Before:
After:
I have:
./nix.sh flake checkto ensure this PR is ready for review.- [ ] Added or updated unit tests.- [ ] Linked a PR or a docs tracking issue to document this change.- [ ] Addedbackport release-x.ylabels to auto-backport this PR.Need help with this checklist? See the cheat sheet.