Simon André
Simon André
The documentation states > You can test how your component is mounted and rendered using the > ``InteractsWithTwigComponents`` trait: A component's contract is that, when called, it returns a string....
You can listen to several events to catch/handle errors, in Symfony UX LiveComponent or directly in stimulus... ... but there is clearly something to improve here in term of DX...
I may find some time to.. but not before mid-week :|
Closing in favor of https://github.com/symfony/symfony/pull/60378 that did find the time. Thank you @pierreboissinot for the early help, sorry to not have found more time on this topic.
It is up to you to decide the size... here are only listed the stricti minimul amount of code for everyone to customize.
I'd be fine adding a row for Tailwind users.
But the main goal is not to for users to add this on every icon, instead we should promote the usage of settings to do so.
What i was saying is that these values are fixed per icon sets, and so should/could be set once instead of copy-pasting things everywhere (and we should not ask users...
If the parent is deferrred, the rendering of its children is deferred too. They are initialized with the value passed by their parent: name
This should work for you: ```twig Parent Component {# Same id as in placeholder #} {# Placeholder is render first and has access to the initial context #} {% macro...