Rename bundles to `UX...Bundle`, and use `AbstractBundle`

[Kocal]

The Problem

Right now, our bundle naming is all over the place. Some bundles have a UX prefix, others don't, and it's confusing.

Bundles with UX prefix:

• UXIconsBundle
• UXMapBundle
• UXToolkitBundle
• UxTranslatorBundle (lowercase x 🤔)

Bundles without UX prefix:

• AutocompleteBundle
• ChartjsBundle
• CropperjsBundle
• DropzoneBundle
• LazyImageBundle (deprecated)
• LiveComponentBundle
• NotifyBundle
• ReactBundle
• StimulusBundle
• SvelteBundle
• SwupBundle (deprecated)
• TogglePasswordBundle (deprecated)
• TurboBundle
• TwigComponentBundle
• TypedBundle (deprecated)
• VueBundle

Why

If I remember correctly, the UX Translator was the first package where I prefixed the bundle name by Ux in #819. Due to skill issue, I assumed that new TreeBuilder('ux_translator') was enough, but nope. 🙈

Then, new packages like Icons, Map and Toolkit used UX (in uppercase), because of "Symfony UX". It would be nice for all packages to follow the same convention based on UX...Bundle.

Also, some bundles use the AbstractBundle (Simpler Bundle Extension and Configuration), but other do not. It would be ideal to re-align all the bundles for using the AbstractBundle, and drop the *Extension and Configuration files.

Migration plan

In 2.x:

• Create UX...Bundle classes
• Use the simplified system based on AbstractBundle
• Remove *Extension and Configuration files (already marked as internal)
• ❓ Keep the old *Bundle files, but use class_alias (e.g.: class_alias(UXAutocompleteBundle::class, AutocompleteBundle::class))
• Changelog

For example:

// UXAutocompleteBundle.php

namespace Symfony\UX\Autocomplete;

class UXAutocompleteBundle extends AbstractBundle {
    // ...
}

// AutocompleteBundle.php

namespace Symfony\UX\Autocomplete;

// So using `Symfony\UX\Autocomplete\AutocompleteBundle::class` in `config/bundles.php` will still works
class_alias(UXAutocompleteBundle::class, AutocompleteBundle::class);

In 3.x:

• Remove the deprecated bundles and aliases
• Changelog

[smnandre]

Yep.. and in 3.x we'll have a UXBundle, so several of these ones will not need to be bundles (exactly how framework bundle and symfony component work together)

But i'd be happy we normalize UX vs Ux 😅 👏

[smnandre]

Well in fact.... to me this is not really worth the work for 2.x

[Kocal]

Yep.. and in 3.x we'll have a UXBundle, so several of these ones will not need to be bundles (exactly how framework bundle and symfony component work together)

in 4.x* :)

[WebMamba]

Not worth for 3.x ?

[smnandre]

For 2.x

And UX Bundle will not be released in 4.0 only :))

[Kocal]

Not worth for 3.x ?

If someone is brave enough to work on it, sure!

[smnandre]

My goal is still the same: have one UX Bundle doing for "front-end" what Framework Bundle does for backend components: registration / DI / configuration.

And i've been waiting 3.x for almost years now ... and cannot wait to enjoy a modern / safe foundation to bring cool components (cool: according to me)

[Kocal]

Let's open a new RFC for the UX Bundle? :)

[smnandre]

Well i’d like we decide on when we release 3.x

I’m not sure we should prépare future for components that do not have one… or files that do not have one. Changing bundle class in 2.x is not something that brings any added value for users using them….. and will get them déprécations without any inventive to upgrade.

(I’m talking only about the bundle classes that should not exist)

[Kocal]

Moved to #3209