Allow referring to root context with `.`

[rossmacarthur]

This could be useful if the root context is not a map, see #22.

There are some questions here though because the root context is not a single map but rather multiple scopes containing values. This would require copying the entire context which could potentially be expensive.

[qq253498229]

Has this feature been released? @rossmacarthur
How should I use the variables passed from the parent template?

parent:

{% include "text-format" with node.children %}

child:

{% for child in . %}
{% if child.category.type | eq: "Text" %}
{{ child.category.text }}
{% endif %}
{% endfor %}

error:

invalid syntax

  --> text-format:1:17
   |
 1 | {% for child in . %}
   |                 ^--
   |
   = reason: expected expression, found member access operator

[rossmacarthur]

It hasn't been implemented. You will have to pass node to the sub template right now.

{% include "text-format" with node %}

{% for child in children %}
{% if child.category.type | eq: "Text" %}
{{ child.category.text }}
{% endif %}
{% endfor %}

[rossmacarthur]

I put some thought into it, there are some outstanding questions:

• What is the expected behaviour with multiple scopes of values, does it always refer to the root context or all of the contexts merged?

{% for k, v in object %}
    {% with k | transform as name %}
        {{ . }} <!-- does this have k, v, name, loop merged into the global context? -->
    {% endwith %}
{% endfor %}

• What is the expected behaviour when using render_from_fn? The options:
  a) passing . directly to the render fn (empty path)
  b) just returning any locally scoped variables (see above)
  c) some combination of these?