$referenceType
argument of the UrlGeneratorInterface::generate
method.
Use the constants defined in the UrlGeneratorInterface
instead.Before:
$router->generate('blog_show', array('slug' => 'my-blog-post'), true);
After:
use Symfony\Component\Routing\Generator\UrlGeneratorInterface;
$router->generate('blog_show', array('slug' => 'my-blog-post'), UrlGeneratorInterface::ABSOLUTE_URL);
ApacheMatcherDumper
and ApacheUrlMatcher
were deprecated and
will be removed in Symfony 3.0, since the performance gains were minimal and
it's hard to replicate the behaviour of PHP implementation.[DEPRECATION] Several route settings have been renamed (the old ones will be removed in 3.0):
pattern
setting for a route has been deprecated in favor of path
_scheme
and _method
requirements have been moved to the schemes
and methods
settingsBefore:
article_edit:
pattern: /article/{id}
requirements: { '_method': 'POST|PUT', '_scheme': 'https', 'id': '\d+' }
<route id="article_edit" pattern="/article/{id}">
<requirement key="_method">POST|PUT</requirement>
<requirement key="_scheme">https</requirement>
<requirement key="id">\d+</requirement>
</route>
$route = new Route();
$route->setPattern('/article/{id}');
$route->setRequirement('_method', 'POST|PUT');
$route->setRequirement('_scheme', 'https');
After:
article_edit:
path: /article/{id}
methods: [POST, PUT]
schemes: https
requirements: { 'id': '\d+' }
<route id="article_edit" pattern="/article/{id}" methods="POST PUT" schemes="https">
<requirement key="id">\d+</requirement>
</route>
$route = new Route();
$route->setPath('/article/{id}');
$route->setMethods(array('POST', 'PUT'));
$route->setSchemes('https');
Before:
$rootCollection = new RouteCollection();
$subCollection = new RouteCollection();
$rootCollection->addCollection($subCollection);
$subCollection->add('foo', new Route('/foo'));
After:
$rootCollection = new RouteCollection();
$subCollection = new RouteCollection();
$subCollection->add('foo', new Route('/foo'));
$rootCollection->addCollection($subCollection);
Also one must call addCollection
from the bottom to the top hierarchy.
So the correct sequence is the following (and not the reverse):
$childCollection->addCollection($grandchildCollection);
$rootCollection->addCollection($childCollection);
RouteCollection::getParent()
and RouteCollection::getRoot()
have been deprecated and will be removed in Symfony 2.3.RouteCollection::addPrefix
method to add defaults, requirements
or options without adding a prefix is not supported anymore. So if you called addPrefix
with an empty prefix or /
only (both have no relevance), like
addPrefix('', $defaultsArray, $requirementsArray, $optionsArray)
you need to use the new dedicated methods addDefaults($defaultsArray)
,
addRequirements($requirementsArray)
or addOptions($optionsArray)
instead.$options
parameter to RouteCollection::addPrefix()
has been deprecated
because adding options has nothing to do with adding a path prefix. If you want to add options
to all child routes of a RouteCollection, you can use addOptions()
.RouteCollection::getPrefix()
has been deprecated
because it suggested that all routes in the collection would have this prefix, which is
not necessarily true. On top of that, since there is no tree structure anymore, this method
is also useless. Don't worry about performance, prefix optimization for matching is still done
in the dumper, which was also improved in 2.2.0 to find even more grouping possibilities.[DEPRECATION] RouteCollection::addCollection(RouteCollection $collection)
should now only be
used with a single parameter. The other params $prefix
, $default
, $requirements
and $options
will still work, but have been deprecated. The addPrefix
method should be used for this
use-case instead.
Before: $parentCollection->addCollection($collection, '/prefix', array(...), array(...))
After:
$collection->addPrefix('/prefix', array(...), array(...));
$parentCollection->addCollection($collection);
added support for the method default argument values when defining a @Route
Adjacent placeholders without separator work now, e.g. /{x}{y}{z}.{_format}
.
Characters that function as separator between placeholders are now whitelisted
to fix routes with normal text around a variable, e.g. /prefix{var}suffix
.
[BC BREAK] The default requirement of a variable has been changed slightly.
Previously it disallowed the previous and the next char around a variable. Now
it disallows the slash (/
) and the next char. Using the previous char added
no value and was problematic because the route /index.{_format}
would be
matched by /index.ht/ml
.
The default requirement now uses possessive quantifiers when possible which improves matching performance by up to 20% because it prevents backtracking when it's not needed.
The ConfigurableRequirementsInterface can now also be used to disable the requirements
check on URL generation completely by calling setStrictRequirements(null)
. It
improves performance in production environment as you should know that params always
pass the requirements (otherwise it would break your link anyway).
There is no restriction on the route name anymore. So non-alphanumeric characters are now also allowed.
[BC BREAK] RouteCompilerInterface::compile(Route $route)
was made static
(only relevant if you implemented your own RouteCompiler).
Added possibility to generate relative paths and network paths in the UrlGenerator, e.g.
"../parent-file" and "//example.com/dir/file". The third parameter in
UrlGeneratorInterface::generate($name, $parameters = array(), $referenceType = self::ABSOLUTE_PATH)
now accepts more values and you should use the constants defined in UrlGeneratorInterface
for
claritiy. The old method calls with a Boolean parameter will continue to work because they
equal the signature using the constants.
urldecode()
calls have been
changed for a single rawurldecode()
in order to support +
for input
paths.