Skip to content

Point that route parameters are also Request attributes #6219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions cookbook/routing/extra_information.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ How to Pass Extra Information from a Route to a Controller
Parameters inside the ``defaults`` collection don't necessarily have to
match a placeholder in the route ``path``. In fact, you can use the
``defaults`` array to specify extra parameters that will then be accessible as
arguments to your controller:
arguments to your controller, and as attributes of the ``Request`` object:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We change this a bit and only tell the reader that we can access the parameters in the controller:

[...] that will then be accessible in your controller::


.. configuration-block::

Expand Down Expand Up @@ -52,12 +52,25 @@ arguments to your controller:

return $collection;

Now, you can access this extra parameter in your controller::
Now, you can access this extra parameter in your controller, as an argument to the controller method::

use Symfony\Component\HttpFoundation\Request;

public function indexAction($page, $title)
{
// ...
}

Alternately, the title could be accessed through the ``Request`` object::

use Symfony\Component\HttpFoundation\Request;

public function indexAction(Request $request, $page)
{
// ...
$title = $request->attributes->get('title');
// ...
}

As you can see, the ``$title`` variable was never defined inside the route path,
but you can still access its value from inside your controller.
but you can still access its value from inside your controller, through the method's argument, or from the ``Request`` object's ``attributes`` bag.