Fix docs typo in Serializers Validators #9563
Merged
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
Pull Request Description
Fix: Correct example for UniqueTogetherValidator in serializer documentation
The example provided for using
UniqueTogetherValidator
in the serializer documentation currently uses anIntegerField
for theroom_number
field. This is incorrect, asUniqueTogetherValidator
is designed to work with relational fields, not integer fields.This pull request replaces the
IntegerField
with aChoiceField
for theroom_number
field, which is a more appropriate field type for this scenario. This change ensures that the example accurately demonstrates how to useUniqueTogetherValidator
with related fields.Changes Made:
room_number
field has been changed from:This minor correction will help users understand how to properly implement
UniqueTogetherValidator
in their serializers.django-rest-framework/docs/api-guide/serializers.md
Line 236 in d3dd45b