Update documentation and tests to change twig:ux:component to twig:UX:Component

[Kocal]

Q	A
Bug fix?	no
New feature?	no
Issues	Fix #...
License	MIT

Applying suggestions for Symfony UX Components section in OP's message, see #2118

[smnandre]

Well.... this wasnt my suggestion ^^

And we made this choice because it felt weird to use <twig:UX:Icon (lower / UPPER / Camel).

Open to change of course, but does not feel the previous topic raised massive interest :)

A2: Symfony UX components should use lowercase casing style in documentation, code blocks, and social media.

😅

[smnandre]

And this would require a lot of other changes since we acted the ux:icon case (commands, docs, website, ...).

Not strongly opiniated here (really) and open to change, but then i guess we should do it all at once, to not confuse dev/users

[smnandre]

This one is a test (the various formats) to ensure we can handle them all

[Kocal]

Oops, good catch

[Kocal]

After a little thought, I understand the problem with the following proposed naming lower:UPPER:PascaleCase (e.g.: twig:UX:Map). I was thinking this way:

• twig, because it's the obligatory prefix for filling in a component
• UX, because Symfony “UX”, and it can be associated with the PascalCase naming of the component
• PascalCase, as documented on https://symfony.com/bundles/ux-twig-component/current/index.html, but also because this convention is the same as with React or Vue (even though Vue also allows kebab-case).

It is true it makes more sense to use <twig:ux:icon>.