You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
One of the major benefits of using RoutingAuto over conventional Symfony routes is that the system has a clear overview about what exists and would not allow one route to replace another.
If you were using standard pattern based routing in routing.yml:
/cms/article/{slug}
and also created a Route object in the hierachy at:
/cms/article/foobar
The two "routes" can co-exist - which is not good.
The text was updated successfully, but these errors were encountered:
One of the major benefits of using RoutingAuto over conventional Symfony routes is that the system has a clear overview about what exists and would not allow one route to replace another.
If you were using standard pattern based routing in routing.yml:
and also created a Route object in the hierachy at:
The two "routes" can co-exist - which is not good.
The text was updated successfully, but these errors were encountered: