Fix EnumSerializer to honor use_enum_values (issue #10570) #1718
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
This change updates the
EnumSerializerin pydantic-core to properly respect theuse_enum_valuesconfiguration flag when serializing PythonEnumtypes. Specifically:use_enum_values: boolfield to theEnumSerializerstruct.use_enum_valuesfrom the model’smodel_configinbuild()(defaulting tofalse).to_python()andjson_key()to unwrap the enum’s.valuewheneveruse_enum_valuesistrue, ensuring that nested models also serialize their enum fields as raw values.use_enum_valuesisfalseor unset.These edits resolve the inconsistency described in Issue #10570 so that enums in nested contexts now correctly output their underlying values.
Related issue number
fix #10570
Checklist
pydantic-core(except for expected changes)