Simon André

Thank you for the nice message ;) Some comments (some more opiniated/personal than others): * As i said, this is the behaviour or the trans_default_domain tag, so nothing we can...

Thank you very much for all these answers, really instructive. I'll answer more deeply when i have time, but i can maybe unlock you with a precision. Twig components (both...

@CMH-Benny oh i totally understand your need, was just illustrating twig component with no embed can be sometimes a good solution :) What i want to insist on is: tthe...

Hi @DRaichev ! Thank you for sharing your experience with UX Turbo and suggesting new features > However it means the new functionality must either be added to the AbstractController,...

After thinking a bit more, this probably should be in a TurboStreamRenderer that one could inject in controller constructor or actions (and in which we could inject Twig) I'm just...

I believe the code example you gave here is not exactly like the IRL scenario you had performance problems with. You render in this example "index.html.twig", right ? ```twig {#...

> I've tried to rewrite the Button.html.twig component to avoid calling nested components, but it didn't help much. The main issue seems to be accessing and rendering blocks. > >...

> Yes, my problem occurs in a real-world application, and Symfony forms are used on the page that is particularly slow. I am using the latest version of the Twig...

There are been some issues with performances with Twig 3.9+ as it offers a great new feature to handle "yield" instead of "echo" (very simplified explanation), that cannot be imposed...

> This results in a 200-300 ms difference in the development scenario (Symfony dev mode with Xdebug enabled). This does not surprise me, but could deserve some warning/documentation.. or probably...