diff options
| author | Marc Tamlyn <marc.tamlyn@gmail.com> | 2012-08-18 12:52:05 +0100 |
|---|---|---|
| committer | Andrew Godwin <andrew@aeracode.org> | 2012-08-18 15:07:21 +0100 |
| commit | f04bb6d798b07aa5e7c1d99d700fa6ddc7d39e62 (patch) | |
| tree | ebb09a427a6f1fb36618877bcbdeb033f8fb5393 /docs | |
| parent | 212b9826bdda5c3c2eb680e6f9c5b046b4172300 (diff) | |
Fixed #17228 -- params context variable is inconsistent
Remove the params variable from the context and just put the variables
in directly.
This had not been committed previously as the original pattern was used
in the functional generic views and we wanted consistency between them,
but django.views.generic.simple.direct_to_template is now gone so we can
do it 'right'.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.5.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt index 29cbd45c49..4f25919d79 100644 --- a/docs/releases/1.5.txt +++ b/docs/releases/1.5.txt @@ -144,6 +144,14 @@ year|date:"Y" }}``. ``next_year`` and ``previous_year`` were also added in the context. They are calculated according to ``allow_empty`` and ``allow_future``. +Context in TemplateView +~~~~~~~~~~~~~~~~~~~~~~~ + +For consistency with the design of the other generic views, +:class:`~django.views.generic.base.TemplateView` no longer passes a ``params`` +dictionary into the context, instead passing the variables from the URLconf +directly into the context. + OPTIONS, PUT and DELETE requests in the test client ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |