#15272: Context object name is translated string
-----------------------------------------+----------------------------------
Reporter: szczav | Owner: nobody
Status: new | Milestone: 1.3
Component: Generic views | Version: SVN
Resolution: | Keywords: generic views
context verbose_name blocker
Triage Stage: Accepted | Has patch: 1
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 1 |
-----------------------------------------+----------------------------------
Comment (by lrekucki):
Replying to [comment:6 szczav]:
> I've removed error message fixes (I'll create separate ticket on this)
and added docs. Way how context variables are created is described in
docs, so I've just rewritten it. By the way
```get_context_object_name()``` description for the
```SingleObjectMixin``` was completely wrong before.
Looks good to me, but didn't actually run it, so someone should take a
look at it.
> Idea of #14018 is good but as I see its milestone is 2.0 so probably we
have to stay with ```object_name``` concept.
Not everything people set on Trac is accurate. IMHO, adding "name_plural"
to Meta is fully backwards compatible. If it's actually worth the small
improvements, is a different matter. But it's also out of scope for 1.3 as
a new feature (could be added in 1.4). It definitely shouldn't block a
release, so going with {{{object_name}}} is the right way here :)
--
Ticket URL: <http://code.djangoproject.com/ticket/15272#comment:8>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
