Small formatting tweaks to named-end-blocks change from [4489]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@4492 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
38f9d8dac6
commit
b9677848f5
|
@ -253,10 +253,15 @@ Here are some tips for working with inheritance:
|
|||
if you want to add to the contents of a parent block instead of
|
||||
completely overriding it.
|
||||
|
||||
* You can optionally name your ``{{ endblock }}`` tag with the same name
|
||||
you gave the ``{{ block }}`` tag (for example, ``{{ endblock content }}``).
|
||||
In larger templates this helps you see which ``{{ block }}`` tags are
|
||||
being closed.
|
||||
* **New in Django development version:** For extra readability, you can
|
||||
optionally give a *name* to your ``{% endblock %}`` tag. For example::
|
||||
|
||||
{% block content %}
|
||||
...
|
||||
{% endblock content %}
|
||||
|
||||
In larger templates, this technique helps you see which ``{% block %}``
|
||||
tags are being closed.
|
||||
|
||||
Finally, note that you can't define multiple ``{% block %}`` tags with the same
|
||||
name in the same template. This limitation exists because a block tag works in
|
||||
|
|
Loading…
Reference in New Issue