Browse files

[1.1.X] Fixed #12946: Removed an invalid example of url tag usage fro…

…m the docs.

r12652 from trunk.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 69fb5c2 commit a6225393c259f7c188c84897282838ebc224a489 @kmtracey kmtracey committed Mar 2, 2010
Showing with 9 additions and 3 deletions.
  1. +9 −3 docs/ref/templates/builtins.txt
@@ -750,12 +750,18 @@ Returns an absolute URL (i.e., a URL without the domain name) matching a given
view function and optional parameters. This is a way to output links without
violating the DRY principle by having to hard-code URLs in your templates::
- {% url arg1,arg2,name1=value1 %}
+ {% url v1,v2 %}
The first argument is a path to a view function in the format
``package.package.module.function``. Additional arguments are optional and
-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.
+should be comma-separated values that will be used as arguments in the URL.
+The example above shows passing positional arguments. Alternatively you may
+use keyword syntax::
+ {% url arg1=v1,arg2=v2 %}
+Do not mix both positional and keyword syntax in a single call. All arguments
+required by the URLconf should be present.
For example, suppose you have a view, ``app_views.client``, whose URLconf
takes a client ID (here, ``client()`` is a method inside the views file

0 comments on commit a622539

Please sign in to comment.