On Sunday, June 24, 2012 12:39:22 PM UTC-5, Georg Brandl wrote:
A good argument for the filter syntax is that its "pipeline" style
> makes the flow and where the filter parameters belong much clearer for
> multiple filters:
>
> {{ var | filter1(f1arg) | filter2(f2arg) | filter3(f3arg) }}
>
> vs
>
> {{ filter3(filter2(filter1(var, f1arg), f2arg), f3arg) }}
>
then the convention can be that the filter produce a result that can pass
another filter, that the filters can be chainables right ?
but i find some inconsistencies in some use of filters and functions.
for example in flask, we have the url_for function global in templates and
i can do {{ url_for('home') }} in my templates but, in Pyramid, we have a
filter for the same function {{ 'home' | url_for }}
--
Yonsy Solis
--
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/pocoo-libs/-/JRgZg67Aj5sJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pocoo-libs?hl=en.
