Replies: 3 comments 1 reply
-
|
Yes, I encountered this issue as well. When the serializer gathers constraints from the model, it doesn’t account for the fact that a constraint might include a custom error message. Additionally, the |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I face to the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
guys, any news? short workarounds? |
Beta Was this translation helpful? Give feedback.
-
|
I created a custom validator by subclassing class CustomUniqueTogetherValidator(UniqueTogetherValidator):
def __call__(self, attrs, serializer):
self.enforce_required_fields(attrs, serializer)
try:
super().__call__(attrs, serializer)
except serializers.ValidationError as exc:
[msg] = exc.detail
raise serializers.ValidationError(
str(msg), code="custom_unique_constraint"
) from exc
class MySerializer(serializers.ModelSerializer):
class Meta:
model = MyModel
fields = "__all__"
validators = [
CustomUniqueTogetherValidator(
queryset=MyModel.objects.filter(...).all(),
fields=["field1", "field2"],
message="My custom message."
),
]If an issue is opened based on this discussion, I’d be happy to submit a PR with a fix. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Example Model
class UniqueTest(BaseModel):
answer = models.ForeignKey(Answer, on_delete=models.CASCADE)
subject = models.ForeignKey(Subject, on_delete=models.CASCADE)
date = models.DateField()
Sample error response for violation
{
"non_field_errors": [
"The fields answer, subject, date must make a unique set."
]
}
Expected error response
{
"non_field_errors": [
"test error message"
]
}
Beta Was this translation helpful? Give feedback.
All reactions