Template range filter
def range( value ):
"""
Filter - returns a list containing range made from given value
Usage (in template):
<ul>{% for i in 3|range %}
<li>{{ i }}. Do something</li>
{% endfor %}</ul>
Results with the HTML:
<ul>
<li>0. Do something</li>
<li>1. Do something</li>
<li>2. Do something</li>
</ul>
Instead of 3 one may use the variable set in the views
"""
return range( value )
Change History
(2)
Resolution: |
→ wontfix
|
Status: |
new → closed
|
Description: |
modified (diff)
|
Easy pickings: |
unset
|
Severity: |
→ Normal
|
Type: |
→ New feature
|
UI/UX: |
unset
|
My impression of this idea is that it is trying to lead to programming in the template. If you have a list of options that need to be rendered, they should be computed in the view, not in the template. If that's as simple as a range of values, then so be it.