Fix serializer method field hidden unique together (#9700) #9710
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.
Fix: SerializerMethodField as HiddenField in unique_together
Corrects an issue where a
SerializerMethodFieldthat shares its namewith a model field involved in a
unique_togetherconstraint (orUniqueConstraint) could be incorrectly treated as aHiddenField.This typically occurred if the underlying model field was nullable or had
a default value, and the
SerializerMethodFieldwas not being correctlyprioritized during the uniqueness metadata processing.
The
ModelSerializer.get_uniqueness_extra_kwargsmethod has been updatedto ensure that if a field name corresponding to a model field in a
uniqueness constraint is explicitly declared as a
SerializerMethodFieldon the serializer, it is not converted into a
HiddenField.A test case has been added to
tests/test_model_serializer.py(
TestSerializerMethodFieldInUniqueTogether) to verify this behavior.