Feature/dev 1101 set new global variables from twig

[brandonkelly]

Description

Adds a new _globals global Twig variable for front-end templates, set to an empty collection. All templates have access to it, and can set/retrieve values on it, providing a way for templates to store custom values in a global scope.

A new set() macro has also been added to collections, which can work as an alias of Collection::put() (key + value arguments), and it also accepts an array of key/value pairs.

{# setting values: #}
{% do _globals.set('foo', 'bar') %}
{% do _globals.set({
  foo: 'bar',
  baz: 'qux',
}) %}

{# getting values: #}
{{ _globals.foo }}
{{ _globals.get('foo') }}
{% dump globals.all() %}

Related issues

• "Request scope" in Craft/Yii? #12951

[linear]

DEV-1101 Set new global variables from Twig templates

It should be possible to define new “global variables” from Twig templates, piggybacking on the new fallback variable support added in 4.4.

[romainpoirier]

Nice add! Do you have any information about performance implications when using global variables?

I'm considering refactoring the values passed to some of my macros so that I can set them from global variables instead of parameters (which remain the same regardless of the context).

Will using a larger number of global variables negatively impact the performance?

[brandonkelly]

@romainpoirier It’s hard to imagine it could have a negative performance impact. In theory the more you’re taking advantage of it, the less values have to be fetched multiple times, so you’d more likely see a performance improvement.