Replace annotations with attributes in code examples

[ker0x]

Currently, the documentation is composed of a mix between annotations and attributes in the different code examples.

For example, the Mercure documentation uses Doctrine attributes while the Serializer documentation use Annotations.
Same goes for the Controller documentation and the Mailer documentation with the Route annotation/attribute!

The support for annotation has been recently dropped in the maker bundle for Entities and the Route attribute is already use when generating Controller,

So, in order to be consistent everywhere, wouldn't it be interesting to replace annotations with attributes when possible?

[javiereguiluz]

After thinking about this, I propose the following:

• Let's keep showing both annotations and attributes in the main article about some topic which uses both
• Let's use only attributes in the other articles not related to that topic

Practical example:

Routing: use annotations + attributes in routing.rst article ... but only use attributes in all the other docs whenever we want to display the route of a controller

Possible exceptions:

Doctrine annotations are quickly disappearing because even the Maker bundle now only generates attributes, so maybe we should only show attributes in all pages.

What do you think? Ping @symfony/team-symfony-docs

[fabpot]

I would use PHP attributes everywhere.

[xabbuh]

I agree with Fabien.

[wouterj]

I would say:

• Show both on the 5.4 docs
• Only use attributes in 6.0+

This way, people can have a look at the LTS docs if they are still using annotations, and we don't have the maintenance burden going forward

[OskarStark]

I agree with @wouterj

[javiereguiluz]

OK, so it seems that there's a consensus around Fabien's idea and Wouter's implementation. Let's do that 🙌

[weaverryan]

Yup - Wouter wins again!

[alexislefebvre]

Maybe pinning this issue would give it visibility and encourage people to update the different pages?