#32219: Use Admin Inline verbose_name as default for Inline verbose_name_plural
-------------------------------------+-------------------------------------
               Reporter:  Siburg     |          Owner:  nobody
                   Type:  New        |         Status:  new
  feature                            |
              Component:             |        Version:  3.1
  contrib.admin                      |       Keywords:  Admin Inline
               Severity:  Normal     |  verbose_name_plural
           Triage Stage:             |      Has patch:  1
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 Django allows specification of a verbose_name and a verbose_name_plural
 for Inline classes in admin views. However, verbose_name_plural for an
 Inline is not currently based on a specified verbose_name. Instead, it
 continues to be based on the model name, or an a verbose_name specified in
 the model's Meta class. This was confusing to me initially (I didn't
 understand why I had to specify both name forms for an Inline if I wanted
 to overrule the default name), and seems inconsistent with the approach
 for a model's Meta class (which does automatically base the plural form on
 a specified verbose_name). I propose that verbose_name_plural for an
 Inline class should by default be based on the verbose_name for an Inline
 if that is specified.

 I have written a patch to implement this, including tests. Would be happy
 to submit that.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32219>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.8be5496c51f2c6debead9c99b02f983c%40djangoproject.com.

Reply via email to