New in Symfony 7.1: Mapped Route Parameters

Contributed by
Nicolas Grekas

in #54720
and #54455.

Symfony maps route parameters to controller arguments automatically since day one.
You only have to use the same name in both places and Symfony does the necessary
data type conversion:

public function showDocument(int $id): Response
// here, $id is an integer variable with the same value as
// the string value included in the URL after ‚/document/‘
// …

When using Doctrine entities, this feature is even more convenient because it
can transform the route parameters into entities via database queries:

// …
use AppEntityDocument;

public function showDocument(Document $document): Response
// using the $id value of the route, Symfony makes a database query
// to find an entity of type Document and whose id matches that value
// (and throws a 404 error if the entity is not found)
// …

This feature works by using all the route parameters in the database query:

public function showDocument(Document $document): Response
// the database query in this case would be:
// $repository = $entityManager->getRepository(Document::class);
// $document = $repository->findOneBy([’slug‘ => ‚the slug‘, ‚id‘ => ‚the id‘, ’name‘ => ‚the name‘]);

This becomes problematic when the controller arguments contain more than one
entity. All route parameters will be used to find all entities, resulting in errors.
You can solve this with the #[MapEntity] attribute but in Symfony 7.1 we’re
introducing Mapped Route Parameters as an alternative.

When adding route parameters, you can now define the mapping between the
route parameter and the controller argument:

public function showDocument(Document $document, Category $category): Response
// the database queries in this case would be:
// $document = $documentRepository->findOneBy([‚id‘ => ‚the id‘, ’name‘ => ‚the name‘]);
// $category = $categoryRepository->findOneBy([’slug‘ => ‚the slug‘]);

This explicit mapping configuration solves the issues when using multiple entities
as controller arguments and is more concise than using the #[MapEntity] attribute.
This mapping also comes in handy when you can’t change the route parameter names
but want to use different controller argument names:

public function handleVoucher(string $voucherCode, string $userAction): Response

Given that this new feature provides a nice DX (developer experience) and is very
concise, we’ve decided to deprecate the automatic mapping of route parameters into
Doctrine entities
starting from Symfony 7.1.

Sponsor the Symfony project.

Symfony Blog

Read More

Latest News


PHP 8.3.8 released!

PHP 8.2.20 released!

PHP 8.1.29 released!

Generated by Feedzy