Fix PydanticTransformer to handle locally-defined nested models #3373
+48
−3
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
model_fieldsinstead oftyping.get_type_hints()inget_literal_typeto handle Pydantic models with forward references to locally-defined classestyping.get_type_hints()fails when it cannot resolve forward references that are not in the module's global namespace (e.g., classes defined inside functions)model_fieldsalready has the resolved type information, making it more robust for these casesTest plan
test_pydantic_model_with_locally_defined_nested_modelthat verifies:get_literal_typeworks with locally-defined nested modelsto_literalserializes the model correctlyto_python_valuedeserializes the model correctly with all values preserved