Changes between Version 4 and Version 5 of TracDev/PortingFromGenshiToJinja

Timestamp:

Feb 22, 2016, 9:39:58 PM (8 years ago)

Author:

Christian Boos

Comment:

a few more examples for setting complex variables

TracDev/PortingFromGenshiToJinja

@@ -36 +36 @@
 
 However, Jinja2 expressions are only //similar// to Python expressions, there are a few differences and limitations, see [http://jinja.pocoo.org/docs/dev/templates/#expressions expressions] doc.
+
+See also [#setcomplexvariabels set complex variables] below for more involved examples.
 
 === include another template
@@ -210 +212 @@
 }}}
 
+If you wonder why the `if all(...)` expression morphed into `if not components|...`, it's because Jinja2 expressions are similar to Python expressions, but not quite the same.
+
+=== set complex variables
 Note that Jinja2 expressions are a subset of Python expressions, and for the sake of simplicity the generator expressions are not part of that subset. This limitation often requires one to make creative use of [http://jinja.pocoo.org/docs/dev/templates/#filters filters], [http://jinja.pocoo.org/docs/dev/templates/#builtin-filters built-in] or custom (`min`, `max`, `trim`, `flatten`).
 
@@ -217 +222 @@
 || `${', '.join([p.name for p in faulty_plugins])}` || \
 || `${faulty_plugins|map('name')|join(', ')}` ||
+|| `sum(1 for change in changes if 'cnum' in change)` || \
+|| `changes|selectattr('cnum')|list|count` ||
+|| `sum(1 for change in changes if 'cnum' not in change)` || \
+|| `changes|rejectattr('cnum')|list|count` ||
 || ... || ... ||