From ee8996d8a6f8fc462a6e912bcf0cf80530704ab4 Mon Sep 17 00:00:00 2001 From: Baptiste Mispelon Date: Fri, 21 Jun 2013 17:46:10 +0200 Subject: [PATCH] [1.5.x] Fixed #20612 -- Fixed incorrect wording in CBV documentation Thanks to ndokos for the report. Backport of b53ed5ac55d5881f129c4921199af355e2b13565 from master. --- docs/topics/class-based-views/generic-display.txt | 13 +++++-------- 1 file 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 8fe6cd0d659..b7a2d10de6d 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