Simon André
Simon André
No worry, we cannot criticize anyone on time things .... 😅 (well, we cannot criticize anyone on anything just to be clear 😄 )
Could you give an example to illustrate ?
So... I'll quote the documentation of [AssetMapper](https://symfony.com/doc/current/frontend/asset_mapper.html) here * [Mapping & Versioning Assets](https://symfony.com/doc/current/frontend/asset_mapper.html#mapping-assets): All files inside of `assets/ `are made available publicly and versioned * [Importmaps](https://symfony.com/doc/current/frontend/asset_mapper.html#importmaps-javascript): A native browser feature...
Do you need those child to be live component ? Could they not be directly properties of the parent one ?
Could you share your IntWrapper code ? Have you tried using a custom hydrateWith / dehydrateWith methods ? Or use the serializer ?
Is there any chance using only name notation could help (by miracle) ? https://github.com/symfony/ux/issues/1851#issuecomment-2181196027
So that mean you should probably try with a collection ... but i'm 40% sure (no more i admit 😅 ) we had some way to handle this :/
> I loved the auto form example, but I’m afraid it would work only as a sample. In practice, you’ll need to define at least the field type to match...
> The entity becomes quite heavy on attributes. A fair point—and one we fully anticipated! 🙂 That said, I don’t believe it’s our role to prevent users from adding attributes...
Is there anything we can do to help merge this PR ?