diff options
| author | Baptiste Mispelon <bmispelon@gmail.com> | 2013-06-21 17:46:10 +0200 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2013-06-21 17:53:10 +0200 |
| commit | ee8996d8a6f8fc462a6e912bcf0cf80530704ab4 (patch) | |
| tree | 16154c1bf337bd251d66b0148d311636a33d4685 | |
| parent | 843802ec269d5c3676a7d3a021539008f8f5233d (diff) | |
[1.5.x] Fixed #20612 -- Fixed incorrect wording in CBV documentation
Thanks to ndokos for the report.
Backport of b53ed5ac55d5881f129c4921199af355e2b13565 from master.
| -rw-r--r-- | docs/topics/class-based-views/generic-display.txt | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/docs/topics/class-based-views/generic-display.txt b/docs/topics/class-based-views/generic-display.txt index 8fe6cd0d65..b7a2d10de6 100644 --- a/docs/topics/class-based-views/generic-display.txt +++ b/docs/topics/class-based-views/generic-display.txt @@ -196,15 +196,12 @@ provided by the generic view. For example, think of showing a list of all the books on each publisher detail page. The :class:`~django.views.generic.detail.DetailView` generic view provides the publisher to the context, but how do we get additional information -in that template. +in that template? -However, there is; you can subclass -:class:`~django.views.generic.detail.DetailView` and provide your own -implementation of the ``get_context_data`` method. The default -implementation of this that comes with -:class:`~django.views.generic.detail.DetailView` simply adds in the -object being displayed to the template, but you can override it to send -more:: +The answer is to subclass :class:`~django.views.generic.detail.DetailView` +and provide your own implementation of the ``get_context_data`` method. +The default implementation simply adds the object being displayed to the +template, but you can override it to send more:: from django.views.generic import DetailView from books.models import Publisher, Book |
