1-33

Symfony2 – Franz Jordán 2011
Route Parameters and Controller Arguments
The route parameters (e.g. {slug}) are especially important because each is made available as
an argument to the controller method:
public function showAction($slug)
{
// ...
}
In reality, the entire defaults collection is merged with the parameter values to form a single
array. Each key of that array is available as an argument on the controller.
In other words, for each argument of your controller method, Symfony looks for a route
parameter of that name and assigns its value to that argument. In the advanced example above,
any combination (in any order) of the following variables could be used as arguments to
theshowAction() method:
$culture
$year
$title
$_format
$_controller
Since the placeholders and defaults collection are merged together, even
the $_controllervariable is available. For a more detailed discussion, see Route Parameters
as Controller Arguments.
You can also use a special $_route variable, which is set to the name of the route that was
matched.
Including External Routing Resources
All routes are loaded via a single configuration file -
usually app/config/routing.yml (see Creating Routes above). Commonly, however, you'll
want to load routes from other places, like a routing file that lives inside a bundle. This can be
done by "importing" that file:
# app/config/routing.yml
acme_hello:
resource: "@AcmeHelloBundle/Resources/config/routing.yml"
When importing resources from YAML, the key (e.g. acme_hello) is meaningless. Just be sure
that it's unique so no other lines override it.
The resource key loads the given routing resource. In this example the resource is the full
path to a file, where the @AcmeHelloBundle shortcut syntax resolves to the path of that
bundle. The imported file might look like this:
# src/Acme/HelloBundle/Resources/config/routing.yml
acme_hello:
pattern: /hello/{name}
defaults: { _controller: AcmeHelloBundle:Hello:index }
63