Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

UniqueTogetherValidator error message should return verbose_name #4134

Closed
@FingerLiu

Description

@FingerLiu

Checklist

  • I have verified that that issue exists against themaster branch of Django REST framework.
  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
  • This is not a usage question. (Those should be directed to thediscussion group instead.)
  • This cannot be dealt with as a third party library. (We prefer new functionality to bein the form of third party libraries where possible.)
  • I have reduced the issue to the simplest possible case.
  • I have included a failing test as a pull request. (If you are unable to do so we can still accept the issue.)

Steps to reproduce

  1. def model with unique_together attr
classCategory(models.Model):name=models.CharField(max_length=20,verbose_name=_('name'))parent=models.ForeignKey('self',related_name='children',verbose_name=_('name'))classMeta:unique_together= ('name','parent',)

and create ModelViewSet for the model
2. create category(name='a', parent=1)
3. call create request with data (name='a', parent=1)

Expected behavior

Since I have setUSE_I18N = True andUSE_L10N = True, and added locale/xxx/django.po correctly.
I expect a error message well translated.

Actual behavior

fields with verbose_name are not translated.
As below
image

I've inspsected the DRF code, there are not any logic dealing with verbose_name inUniqueTogetherValidator.
Currently it just get field name of serializer field and return it to error_message of UniqueTogetherValidator.
As blow
https://github.com/tomchristie/django-rest-framework/blob/master/rest_framework/validators.py#L149

Is this by purpose or by mistake?
I can try to make a PR with test case and fix if it is needed.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp