By what channel can the community be kept aware of the change on specification?

[ericmorand]

Hi Twig community.

I discovered today that since spec 2.14 (alongside 1.44 and 3.1) Twig supports instanciating a hash with just a value:

133edb3

The documentation was also updated at some point:

{# keys can be omitted if it is the same as the variable name #}
{ foo }
{# is equivalent to the following #}
{ 'foo': foo }

It is not the first time that the community discovers a change in the langage specification way after it is implemented by TwigPHP.

I think it would make our life much more comfortable if there was a way to communicate these changes before they are implemented or just when they are implement by TwigPHP so that we don't lose track of langage features: going back in time to try and list all the changes that happened is long, painful and unreliable.

Is there such a channel that we could join to be made aware of those changes?

If not, would it be possible to create one and leverage the open source collaboration that we all cherish? 🙂

[xabbuh]

There is no such thing as a Twig specification. All the activity happens in this repository. If you watch the issues and pull requests, you will be up-to-date with how Twig evolves.

[ericmorand]

But how are merge request approved if there is no upstream specification?

[stof]

The discussion happens in the pull requests on that repo.
This repo is the source of truth for the Twig language.

[ericmorand]

OK, noted. I've subscribed. Is there always an issue before an MR?

[xabbuh]

not necessarily