Simon André

Oh and i also think the first one makes the more sense

Hey @pierredup ! Thank you for this nice PR Hot reaction: I'm indeed not sure we want to enable such behaviour without some opt-in/out first :) Couple of questions /...

Thank you @javiereguiluz! I think this is very good example of what the "reuse/symbol" we're working on (see #1800) can solve. And it demonstrate the importance to add steps in...

I've been thinking a lot about this PR and the nice work done here.. What if we use a flag/argument for a first version ? Something like ```twig {# Twig...

I'm thinking of 4 things here: - cache (file or config) that people will not know about - n/bad access to network during twig cache build (this would make the...

@pierredup I was going to add the configuration I asked for and merge this PR ... .. but two things during my tests **1/** the HTML syntax is not precompil-_able_...

Well i had my concerns... so i just made too a "quick benchmark" And the difference is, to me, almost non existant. And way lower than any of the digits...

> This package can just provide the UXIconFunction class, with some instructions in the documentation on how to use it with a custom twig function if someone wants to I...

> ux_icon_inline That is much easier in term of communication. And could be easily enabled/disabled in dev/debug, with a dedicated custom Twig Runtime and no penalty for other users.

As i told @kbond multiple times: only a fraction of users will benefit from this feature, so even minor drawbacks need careful consideration. Thank you very much for your work...