New in Symfony 5.4: Route Aliasing

Contributed by Jérôme Parmentier in #38464.

When refactoring applications, especially if you work on a legacy application, it's common to need to change the name of some routes. Some renames might be considered cosmetic (e.g. rename admin_dashboard to admin) but others are essential for the new application because they change the route name pattern entirely (e.g. rename api_register_customer_requests_post_collection to sylius_shop_api_register). The need to rename routes is increasingly popular among Symfony developers and that's why in Symfony 5.4, we're improving the Routing component to allow aliasing routes. In any route configuration, add the alias option and provide the name of the route which is equivalent to it. For example:

    1

2 3 4 5 6 7 8 9

config/routes.yaml

this is the existing and 'legacy' route

admin_dashboard:

...

this is the new route that replaces the old one

admin: alias: admin_dashboard

...

The admin route is considered by Symfony the same as admin_dashboard and you can generate the same URLs with both of them. The above example uses YAML, but it works with all the other route configuration formats as well (PHP, XML).

Deprecating Routes An added bonus of this feature is that you can deprecate routes and tell users in advance so they can update their applications. Imagine that you publish a third-party bundle that includes a route called user_collection_index and you want to rename it to users_index. Instead of just renaming the route (which would break all applications using the bundle) define the old route as an alias of the new route and add to it the deprecated option:

    1

2 3 4 5 6 7 8 9 10

config/routes.yaml

users_index:

...

user_collection_index: alias: 'users_index' deprecated: package: 'some-vendor/some-package' version: '3.14'

...

If any application uses the user_collectionindex route to generate URLs, they'll see the following deprecation message: "Since some-vendor/some-package 3.14: The "user_collectionindex" route alias is deprecated. You should stop using it, as it will be removed in the future." Add the message option under deprecated if you want to customize the deprecation message entirely.

                Sponsor the Symfony project.

http://feedproxy.google.com/~r/symfony/blog/~3/EfT_bp2dO8Y/new-in-symfony-5-4-route-aliasing

Created 4y | Nov 9, 2021, 8:20:10 AM


Login to add comment

Other posts in this group

SymfonyOnline June 2025: Detect Hidden Defects: Check Your PHP Tests

SymfonyOnline June 2025 is almost here, starting in almost 2 months on:

June 10-11: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings. June 12-13: Online confe

May 8, 2025, 2:40:19 PM | Symfony
New in Symfony 7.3: JsonPath Component

Contributed by Alexandre Daubois in

May 8, 2025, 10:10:10 AM | Symfony
SymfonyOnline June 2025: Combining Turbo, LiveComponent & Stimulus... the Right Way?

SymfonyOnline June 2025 is almost here, starting in almost 2 months on:

June 10-11: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings. June 12-13: Online confe

May 7, 2025, 1:10:15 PM | Symfony
New in Symfony 7.3: New and Improved Console Helpers

Symfony 7.3 introduces powerful improvements to the Console component, beyond the much-anticipated invokable commands and input attributes. This version also brings new helpers and features designed t

May 7, 2025, 8:30:04 AM | Symfony
New in Symfony 7.3: Static Error Pages

Contributed by Loick Piera in

May 6, 2025, 9:20:10 AM | Symfony
New in Symfony 7.3: Simpler Server Event Streaming

Contributed by Yonel Ceruto in

May 5, 2025, 7:50:03 AM | Symfony
A Week of Symfony #957 (April 28 – May 4, 2025)

This week, Symfony 6.4.21 and 7.2.6 maintenance versions were released. In addition, we published the first beta of Symfony 7.3 so you can test it in your own apps before its final release at the end

May 4, 2025, 8:40:05 AM | Symfony