Fix empty list default for GraphQL list fields #2957
Closed
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.
Summary
[String!]! = []) now correctly generateField(default_factory=list)instead ofField(...)[String!] = []) now correctly generateField(default_factory=list)instead ofField([])Problem
When GraphQL input types have fields with empty list defaults like:
The generated Pydantic code was incorrect:
Field(...)- completely ignored the defaultField([])- used mutable default directly (anti-pattern)Solution
_get_default_as_pydantic_model()for any list type with empty default__str__()to not skip default handling whenrequired=Truebuthas_default=True...when there's already adefault_factoryTest plan
test_main_graphql_empty_list_defaultwith both Pydantic v1 and v2 variants🤖 Generated with Claude Code