35
{% if bCat2 == True %}
    <div>True</div>
{% else %}
    <div>False</div>

Returns <div>False</div> even when bCat2 is True. Thanks, Andrew

ljs.dev
  • 4,449
  • 3
  • 47
  • 80
Andrew Kloos
  • 4,189
  • 4
  • 28
  • 36

6 Answers6

66

This part of documentation can help you:

The special constants true, false and none are indeed lowercase. Because that caused confusion in the past, when writing True expands to an undefined variable that is considered false, all three of them can be written in title case too (True, False, and None). However for consistency (all Jinja identifiers are lowercase) you should use the lowercase versions.

Source: http://jinja.pocoo.org/docs/templates/

Try that code:

{% if bCat2 == true %}
<div>True</div>
{% else %}
<div>False</div>
{% endif %}
Nelson G.
  • 5,145
  • 4
  • 43
  • 54
Evgeni Nabokov
  • 2,421
  • 2
  • 32
  • 36
43

Option 1: Most common solution

Solve that like python do.

Check if variable is true

{% if bCat2 %}
    <div>True</div>
{% else %}
    <div>False</div>

Check if variable is false

{% if not bCat2 %}
    <div>False</div>
{% else %}
    <div>True</div>

Jinja2 If documentation

Option 2: Jinja2 sameas solution

Solve like jinja2 do. Becareful with boolean lowercase.

Check if variable is true

{% if bCat2 is sameas true %}
    <div>True</div>
{% endif %}

Check if variable is false

{% if bCat2 is sameas false %}
    <div>False</div>
{% endif %}

Jinja2 sameas documentation

mrroot5
  • 1,811
  • 3
  • 28
  • 33
  • 2
    For those stumbling over this: When your put the boolean variable in --extra-vars(of ansible-playbook), don't do it this way: `--extra-vars="bCat2=True"`. This won't work, because the command line app makes a bCat2 var with type string. Better is to use json here: `--extra-vars='{ "bCat2": true }'`. – ferdy Sep 15 '18 at 23:02
  • Or you could give the var an empty val and that will be interpreted as false. Like so: `--extra-vars='bCat2='` – UlfR May 21 '21 at 05:27
14

The proper way to do this in Jinja2 is:

{% if bCat2 is sameas true %}
    <div>True</div>
{% elif bCat2 is sameas false %}
    <div>False</div>
{% endif %}

The reason why you cannot do 

{% if bCat2 == true %}

is that if bCat2 == 1 or bCat2 == 1.0 it will also be considered True.

Dag Wieers
  • 1,663
  • 13
  • 11
11

To test a Boolean variable in a template, convert it to a string in Python

str(bCat2)

and then compared it to a string in the template

{% if bCat2 == 'True' %}
    <div>True</div>
{% else %}
    <div>False</div>
drs
  • 5,679
  • 4
  • 42
  • 67
Andrew Kloos
  • 4,189
  • 4
  • 28
  • 36
  • 3
    But it's better to compare directly in Jinja2, without converting the boolean to a string, not @Andrew? I think the @mrroot5 answer would be the easier and better way to test if a boolean is true or false. Just for curiosity, why should someone lean towards the solution you propose? – Ivanhercaz Sep 19 '18 at 22:43
3

I would like to add that if your logic is a bit more complex you might want to read about scopes.

As mentioned in official documentation:

As of version 2.10 more complex use cases can be handled using namespace objects which allow propagating of changes across scopes:

{% set ns = namespace(found=false) %}
{% for item in items %}
    {% if item.check_something() %}
        {% set ns.found = true %}
    {% endif %}
    * {{ item.title }}
{% endfor %}
Found item having something: {{ ns.found }}
Pitto
  • 8,229
  • 3
  • 42
  • 51
1

take this:

{% if bCat2 is true %}
    <div>True</div>
{% else %}
    <div>False</div>
{% endif %}

my test:

$ python -m pip install j2cli
$ j2 <(echo "{% if false is true %}
    <div>True</div>
{% else %}
    <div>False</div>
{% endif %}")

    <div>False</div>

$ j2 <(echo "{% if true is true %}
    <div>True</div>
{% else %}
    <div>False</div>
{% endif %}")

    <div>True</div>
Oliver Gaida
  • 1,722
  • 7
  • 14