You cannot make a {% block %} conditional; once you use the tag, the block is always going to be filled in. Put your conditional inside the block instead, and use super() to instruct Jinja to use the original contents of the block as defined in the template: {% extends “base.html” %} {% block content … Read more
I find the magic map extract here. main_nodes_ips: “{{ groups[‘mainnodes’] | map(‘extract’, hostvars, [‘ansible_host’]) | join(‘,’) }}” main_nodes_ips_with_port: “{{ groups[‘mainnodes’] | map(‘extract’, hostvars, [‘ansible_host’]) | join(‘:3000,’) }}:3000” An alternative(idea comes from here): main_nodes_ips: “{{ groups[‘mainnodes’] | map(‘extract’, hostvars, [‘ansible_eth0’, ‘ipv4’, ‘address’]) | join(‘,’) }}” (Suppose the interface is eth0)
I think your best bet is a combination of defined() check along with looking at the length of the array via length() function: {% if texts is defined and texts|length > 0 %} … {% endif %}
In new versions of Jinja2 (2.9+): {{ value if value }} In older versions of Jinja2 (prior to 2.9): {{ value if value is not none }} works great. if this raises an error about not having an else try using an else .. {{ value if value is not none else ” }}
Turns out that + and – are there for whitespace control purpose. You can manually disable the lstrip_blocks behavior by putting a plus sign (+) at the start of a block […] You can also strip whitespace in templates by hand. If you put an minus sign (-) to the start or end of an … Read more
You can use the length filter: {% if some_var|length > 1 %}
There are a few global variables that are passed in the templates context by default by flask (here is the complete list), one of them being config, which allows you to access the application configuration from templates. Being a dictionary, it can be accessed using the syntax config[‘MY_CONFIGURATION’] or config.MY_CONFIGURATION (this syntax for accessing dict … Read more
As long as you’ve imported request, request.path should contain this information.
The trick is that kwargs has to be accessed at least once in any macro that should accept them. That is to say, you must call {{ kwargs }} once in macro body without declaring it in macro argument list. The same is true for {{ varargs }}. This will not work {% macro example_2(one, … Read more
Within the template, no, you cannot import python code. The way to do this is to register the function as a jinja2 custom filter, like this: In your python file: from dates.format import timesince environment = jinja2.Environment(whatever) environment.filters[‘timesince’] = timesince # render template here In your template: {% macro time(mytime) %} <a title=”{{ mytime }}”>{{ … Read more