Releases: symfony-cmf/Routing
Releases · symfony-cmf/Routing
3.0.3
3.0.2
3.0.1
3.0.0
- [BC Break] Removed deprecated VersatileRouterInterface::supports, as only string route names are
allowed since Symfony 6. - [BC Break] As with Symfony itself, the route name now must be a
string
. As noted in
the changes for CMF Routing 2.3, to generate a route from an object is to use
RouteObjectInterface::OBJECT_BASED_ROUTE_NAME
(cmf_routing_object
) as
route name and pass the route object in the parameters with key
RouteObjectInterface::ROUTE_OBJECT
(_route_object
). - [BC Break] Added static type declarations to interfaces and classes.
- Revoked the deprecation on Router::match because Symfony keeps offering the match without request
object. - Support Symfony 6, dropped support for older Symfony versions.
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
- Dropped support for PHP 7.1 and Symfony 3.4 and 4.3.
- Added support for Symfony 5.
- Deprecated passing a route object (or anything else that is not a string) as
the$name
parameter in thegenerate
method of the ChainRouter and the
DynamicRouter. Symfony 5 enforces the$name
parameter to be a string with
static type declaration.
The future proof way to generate a route from an object is to use the route
nameRouteObjectInterface::OBJECT_BASED_ROUTE_NAME
(cmf_routing_object
)
and pass the route object in the parameters with key
RouteObjectInterface::ROUTE_OBJECT
(_route_object
). - The VersatileGeneratorInterface::supports method is deprecated as it was used
to avoid errors with routers not supporting objects in$name
.