Customizing the Dynamic Router

Edit this page

The DynamicRouter is built to be customized. Both route matching and URL generation services can be injected, and the provided route matcher and URL generator classes are built to be further customizable.

This chapter describes the most common customization. If you want to go further, you will need to read the component documentation and look into the source code.

If the DynamicRouter does not fit your needs at all, you have the option of writing your own routers to hook into the ChainRouter.

Writing your own Route Enhancers

You can add your own RouteEnhancerInterface implementations if you have a case not handled by the provided enhancers.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
// src/AppBundle/Routing/Enhancer/SimpleEnhancer.php
namespace AppBundle\Routing\Enhancer;

use Symfony\Cmf\Component\Routing\Enhancer\RouteEnhancerInterface;
use Symfony\Component\HttpFoundation\Request;

class SimpleEnhancer implements RouteEnhancerInterface
{
    public function enhance(array $defaults, Request $request)
    {
        // ... customize the $defaults array

        return $defaults;
    }
}

Simply define services for your enhancers and tag them with dynamic_router_route_enhancer to have them added to the routing. You can specify an optional priority parameter on the tag to control the order in which enhancers are executed. The higher the priority, the earlier the enhancer is executed.

1
2
3
4
5
6
# app/config/services.yaml
services:
    app.routing.simple_enhancer:
        class: AppBundle\Routing\Enhancer\SimpleEnhancer
        tags:
            -  { name: dynamic_router_route_enhancer, priority: 10 }

Using a Custom Route Provider

The Dynamic Router allows you to customize the Route Provider (i.e. the class responsible for retrieving routes from the database) and, by extension, the Route objects.

Creating the Route Provider

The route provider must implement the RouteProviderInterface. The following class provides a simple solution using an ODM Repository.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
// src/AppBundle/Repository/RouteProvider.php
namespace AppBundle\Repository;

use Doctrine\ODM\PHPCR\DocumentRepository;
use Symfony\Cmf\Component\Routing\RouteProviderInterface;
use Symfony\Component\Routing\RouteCollection;
use Symfony\Component\Routing\Route as SymfonyRoute;

class RouteProvider extends DocumentRepository implements RouteProviderInterface
{
    /**
     * This method is used to find routes matching the given URL.
     */
    public function findManyByUrl($url)
    {
        // for simplicity we retrieve one route
        $document = $this->findOneBy([
            'url' => $url,
        ]);

        $pattern = $document->getUrl(); // e.g. "/this/is/a/url"

        $collection = new RouteCollection();

        // create a new Route and set our document as
        // a default (so that we can retrieve it from the request)
        $route = new SymfonyRoute($pattern, [
            'document' => $document,
        ]);

        // add the route to the RouteCollection using
        // a unique ID as the key.
        $collection->add('my_route_'.uniqid(), $route);

        return $collection;
    }

    /**
     * This method is used to generate URLs, e.g. {{ path('foobar') }}.
     */
    public function getRouteByName($name, $params = [])
    {
        $document = $this->findOneBy([
            'name' => $name,
        ]);

        if (!$document) {
            throw new RouteNotFoundException("No route found for name '$name'");
        }

        $route = new SymfonyRoute($document->getUrl(), [
            'document' => $document,
        ]);

        return $route;
    }
}

Tip

As you may have noticed we return a RouteCollection object - why not return a single Route? The Dynamic Router allows us to return many candidate routes, in other words, routes that might match the incoming URL. This is important to enable the possibility of matching dynamic routes, /page/{page_id}/edit for example. In our example we match the given URL exactly and only ever return a single Route.

Replacing the Default CMF Route Provider

To replace the default RouteProvider, it is necessary to modify your configuration as follows:

1
2
3
4
# app/config/packages/cmf_routing.yaml
cmf_routing:
    dynamic:
        route_provider_service_id: app.route_provider

Where app.route_provider is the service ID of your route provider. See Creating and configuring services in the container for information on creating custom services.

Using a Custom URL Generator

The dynamic router can also generate URLs from route objects. If you need to customize this behavior beyond what the route generate event allows, you can implement the Symfony\Component\Routing\Generator\UrlGeneratorInterface yourself and configure that service:

1
2
3
4
# app/config/packages/cmf_routing.yaml
cmf_routing:
    dynamic:
        url_generator: app.my_url_generator

The RouteDefaultsValidator

The route getDefaults method has a RouteDefaults constraint. When a route is validated, the RouteDefaultsValidator will be called. If the _controller or the _template defaults are set, the validator will check that they exist.

You can override the validator by setting the cmf_routing.validator.route_defaults.class parameter.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.
TOC
    Version