Simon André

I'm very eager to change radically this system the second 3.X is released, but it will not be easy. Every attempt i made to handle these questions (blockstack, deterministic id,...

I'm strongly opposed to introducing the UX bundle in 2.x, and I'm honestly a bit shocked by this. We agreed months ago to release 3.x first, to clear all deprecations...

> 1. should we create a new package for that? Absolutely. Stimulus wires JavaScript. UXBundle wires UX :)

> 2\. Symfony provides Bundles and Components in https://github.com/symfony/symfony, do we have some packages that can't become components but must stays bundles? As I see it, Toolkit maybe (depending on...

> This would have the following advantages: > centralizing the configuration of Symfony UX packages, > pooling certain logic, e.g., “is AssetMapper installed?”, “add this path to AssetMapper,” etc., >...

- discarding the coupling that makes “Symfony UX” synonymous with “Stimulus”, - making it possible to add a small but impactful Twig feature once and benefit everywhere (e.g. a default...

And ... providing a stable extension point __**in the future**__, offering community packages a standardized way to plug into the ecosystem via shared events and conventions.

There isn’t much choice for the rollout: - ship UXBundle in 3.x as experimental, - deprecate the legacy per-package bundles in 3.x (with an easy migration path), - make UXBundle...

Almost forgot one of the biggest motivation: DX. ``` # interactive setup (pick what you want, apply the right wiring/config) symfony bin/console ux:install # checks the packages json / yarn...

Well, it's hard to answer your last point without giving a full presentation of "what I think UX could or should be today, next month, next year, ..." But i'll...