Are global variables part of the context or not?

[ericmorand]

According to this documentation, it is possible to declare global variables to the PHP compiler:

https://twig.symfony.com/doc/3.x/advanced.html#globals

A global variable is like any other template variable, except that it's available in all templates and macros:

It is not clear though if these variables are part of the context or not.

Specifically if they are part of the context, they must not be passed to included templates when with_context is passed as false, as per documentation of the include function:

You can disable access to the context by setting with_context to false

But if they are not part of the context, then they must not be part of the content of the _context global variable as per documentation:

_context: references the current context;

Can someone please clarify this point?

Note also the confusing naming by the way between global variables passed by executing addGlobal and...global variables like _context that are always available.

What is the nuance between the two concepts of global variables?

[stof]

They are added in the context for each template. So even when you don with_context=false, they are still there (they are not forwarded from the caller by the include function, but they are still inserted in the context by the Environment as they are global variables)

[ericmorand]

So, they are not part if the context, are they?

If if they are not, they are not part of the _context variable either, are they?

[xabbuh]

Global variables are part of the _context variable inside the included template.

[stof]

Well, inside a template, they are part of the context (so they appear in _context). But the Environment injects global variables in the context of all templates being rendered, not only of templates being rendered from elsewhere than another template. So global variables will always be in this context.

[ericmorand]

Thanks a lot. Can I assume that the correct phrasing for the with_context argument is:

You can disable access to the context of the caller by setting with_context to false

[stof]

yes