Christophe Coevoet

how does this interact with the `Prompt` attribute added in version 7.4 ?

To me, the component standalone usage should show how to register those in an Application actually (which will probably show that those are much more cumbersome to use than the...

> it will need to check `$input->getArgument('command')` to distinguish the executed command. This is a bad advice because the Application class supports resolving commands using any non-ambiguous shortened name passed...

To me, this is a general issue in the shape generator. Any field marked as required in the Configuration definition is required __after merging__, not in each file providing configuration....

yeah indeed. When performing no deep merging on a node, a required child of that node indeed becomes each time it is configured (well, Symfony will validate only the last...

There is no good way to implement support for provider-maintained templates in the Mailer component because the template features of the providers are not interoperable (not even talking about the...

@that-guy-iain "json array" is not enough to determine that they are interoperable. The question is whether the transports could build those json arrays from the **same** input (the one that...

The PHP API to define variables is **not** an implementation detail. It is the public API to use that feature (otherwise, we would only supports rendering a template without passing...

You are asking us to support service provider templates, not Twig templates. And in `symfony/mailer`, projects are not using a specific service provider. The whole promise of the component is...

> It is possible to use **ancho** instead of **anchura**, This change was requested by other reviewers in github.com/symfony/symfony/pull/62239