Fixed #4355 -- Clarified a confusing example in the use of the url template

tag. Based on a patch from Collin Grady.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@5353 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-05-26 09:43:32 +00:00
parent c1efc3cd9f
commit aae36cfc8e
1 changed files with 5 additions and 4 deletions

View File

@ -843,10 +843,11 @@ The first argument is a path to a view function in the format
should be comma-separated values that will be used as positional and keyword should be comma-separated values that will be used as positional and keyword
arguments in the URL. All arguments required by the URLconf should be present. arguments in the URL. All arguments required by the URLconf should be present.
For example, suppose you have a view, ``app_name.client``, whose URLconf takes For example, suppose you have a view, ``app_views.client``, whose URLconf
a client ID. The URLconf line might look like this:: takes a client ID (here, ``client()`` is a method inside the views file
``app_views.py``). The URLconf line might look like this::
('^client/(\d+)/$', 'app_name.client') ('^client/(\d+)/$', 'app_views.client')
If this app's URLconf is included into the project's URLconf under a path If this app's URLconf is included into the project's URLconf under a path
such as this:: such as this::
@ -855,7 +856,7 @@ such as this::
...then, in a template, you can create a link to this view like this:: ...then, in a template, you can create a link to this view like this::
{% url app_name.client client.id %} {% url app_views.client client.id %}
The template tag will output the string ``/clients/client/123/``. The template tag will output the string ``/clients/client/123/``.