Simon André
Simon André
What i like in the idea of @Guikingone is that using an dedicated attribute is an active choice, that cannot hide some unwanted / hidden behaviour
We need to refactor the entire hydration/serialisation system sooner than later (TypeInfo, etc) ... but a first version or DTO in events before UX 3 (if that does not change...
You can look how i did it for the icon modals on this page: https://ux.symfony.com/icons (source code is in the repository) I agree with you this is a frequent pattern,...
⚠️ reminder to not push before 7.2 (i know it's obvious.. but we will release a 2.20 soon so i rather say it ^^)
This will need to be updated if we change anything in the extension, add a pass, etc etc.. Seems a bit risky, but in the same time in understand the...
To be honest it's not something easy to check/debug/dev without having such access to such kit :|
@simondaigre in the future there could be here a great extension point for this use case. But don't count on it "now".. this won't be for the first version(s?)
Hmm not enough... it would require to change a lot of AssetMapper code to allow not one but _two_ new concepts.. - the npm and npm locally (so .... node_modules...
If you want to check, started some work was done here https://github.com/symfony/symfony/pull/58722 (and was waiting for people to step in and help, so really glad you did here 👍 )
@OskarStark Of course!