Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Fixed #13608 - Noted that template lookups use literal values.

  • Loading branch information...
commit 74c025d0285450bf277afbee095172af54562ab6 1 parent 5faadea
Tim Graham timgraham authored
Showing with 9 additions and 1 deletion.
  1. +4 −0 docs/ref/templates/api.txt
  2. +5 −1 docs/topics/templates.txt
4 docs/ref/templates/api.txt
View
@@ -125,6 +125,10 @@ dot in a variable name, it tries the following lookups, in this order:
* Attribute lookup. Example: ``foo.bar``
* List-index lookup. Example: ``foo[bar]``
+Note that "bar" in a template expression like ``{{ foo.bar }}`` will be
+interpreted as a literal string and not using the value of the variable "bar",
+if one exists in the template context.
+
The template system uses the first lookup type that works. It's short-circuit
logic. Here are a few examples::
6 docs/topics/templates.txt
View
@@ -102,7 +102,7 @@ Use a dot (``.``) to access attributes of a variable.
attempts to loop over a ``collections.defaultdict``::
{% for k, v in defaultdict.iteritems %}
- Do something with k and v here...
+ Do something with k and v here...
{% endfor %}
Because dictionary lookup happens first, that behavior kicks in and provides
@@ -116,6 +116,10 @@ If you use a variable that doesn't exist, the template system will insert
the value of the :setting:`TEMPLATE_STRING_IF_INVALID` setting, which is set
to ``''`` (the empty string) by default.
+Note that "bar" in a template expression like ``{{ foo.bar }}`` will be
+interpreted as a literal string and not using the value of the variable "bar",
+if one exists in the template context.
+
Filters
=======
Please sign in to comment.
Something went wrong with that request. Please try again.