tjsmith-meta
tjsmith-meta
## Description / Reproduction steps The following template behaves differently with MiniJinja 2.3.1 vs Python Jinja2 2.11.3. ``` {{ ('hello', 'world') | join(d=' ') }} ``` MiniJinja output: `hello{"d": "...
The following template loads and renders fine with Python jinja2, but crashes with jinja2cpp. ``` {% if 'foo' == 'bar'%} 1 {% elif 'foo' == 'foo' %} 2 {% else...
The jinja2 spec alludes to two flavors of format -- `str.format` and `str|format` -- that seemingly have / support different string formatting syntaxes. https://jinja.palletsprojects.com/en/2.10.x/templates/ The `str.format` syntax appears to support...
Python jinja2 renders True/False/None values capitalized, whereas jinja2cpp renders True/False lowercased, and None renders as empty string. Here's a template that demonstrates. ``` {% set foo = True %} {%...
Here's the example template that works in Python jinja2 -- 'is not defined'. ``` {% if foo is not defined %} not defined {% endif %} {% set foo =...
Appears to work in Python jinja2, and there's a Note that mentions it in this section in the docs. https://jinja.palletsprojects.com/en/2.10.x/templates/#literals Here's a template example that works in Python and crashes...
The following template compiles with Python jinja2 (and yields an output of "1"), but does not work with jinja2cpp. ``` {% if 0, 'foo' != 'bar' %} 1 {% endif...
Looks like jinja2cpp just doesn't match the spec here on parsing dict/map literals. https://jinja.palletsprojects.com/en/2.10.x/templates/#literals Here's what works in Python (but doesn't work with jinja2cpp). ``` {% set foo = {"bar":"baz"}...
The following template (`foo in (...)`) compiles fine in both Python jinja2 and Jinja2Cpp. ``` {% macro foo(val) %} {{1 if val in ('', "''", 'foo')}} {% endmacro %} ```...
Render discrepancies with Python Jinja2 (none vs None, true vs True, double vs single quotes, tuple)
I had created an issue previously for this here. https://github.com/mitsuhiko/minijinja/issues/660 I already commented on that closed issue, but thought folks may not see the latest comment due to it being...