Contributed by Renan de Lima in #44405.
Routing in Symfony applications is usually simple and consists of mapping some controller method to some URL path. However, sometimes you need to evaluate complex conditions to decide if some incoming URL should match a given controller. That's why Symfony allows using expressions to match routes. In Symfony 6.1 we've improved routing conditions so you can also call services inside those expressions. To do that, use the new service() function and pass the name of the service to call:
// src/Controller/DefaultController.php
namespace App\Controller;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController; use Symfony\Component\HttpFoundation\Response; use Symfony\Component\Routing\Annotation\Route;
class DefaultController extends AbstractController {
[Route(
'/some-path',
name: 'some_name',
condition: "service('some_service').someMethod()",
)]
public function someControllerMethod(): Response
{
// ...
}
}
By default, and for performance reasons, you cannot call any of the services defined in your application. Instead, you must add the routing.condition_service tag or the #[AsRoutingConditionService] attribute to those services that will be available in route conditions:
use Symfony\Bundle\FrameworkBundle\Routing\Attribute\AsRoutingConditionService;
// ...
[AsRoutingConditionService(alias: 'some_service')]
class SomeService { public function someMethod(): bool { // ... } }
The alias option defines how this service will be referred to inside the expression, so you don't have to use the full service name (which is usually too long).
Sponsor the Symfony project.
Login to add comment
Other posts in this group
SymfonyOnline June 2024 is just around the corner and will start on:
June 4-5: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings! June 6-7: Online conference
SymfonyLive Berlin 2024 is just around the corner and will start on June 20-21. Get ready for the impressive lineup of speakers and topics. Visit here to more details and don't miss out on this
Symfony 7.1.0-BETA1 has just been released. Here is the list of the most important changes since 7.0:
feature #54818 [Translation] Crowdin is backing its translation bridge, thanks to them! \o/ (
SymfonyOnline June 2024 is just around the corner and will start on:
June 4-5: Workshop days. It is possible to attend 1 two-day training or 2 one-day trainings! June 6-7: Online conference d
SymfonyLive Berlin 2024 is just around the corner and will start on June 20-21. Get ready for the impressive lineup of speakers and topics. Visit here to more details and don't miss out on this
Symfony 7.0.7 has just been released. Here is the list of the most important changes since 7.0.6:
bug #54699 [DoctrineBridge] Update AbstractSchemaListener to adjust more database params (@ywisax
Symfony 5.4.39 has just been released. Here is the list of the most important changes since 5.4.38:
bug #54751 [Validator] detect wrong e-mail validation modes (@xabbuh)
bug #54723 [Form] read f