@@ -346,14 +346,14 @@ The example in this section applies if you use the ORM route provider
346
346
``staticPrefix `` field of the
347
347
``Symfony\Cmf\Bundle\RoutingBundle\Doctrine\Orm\Route `` to find route candidates.
348
348
349
- Symfony Cmf routing system allows us loading whatever content from a route.
350
- That means an entity route can reference to different types of entities.
351
- But Doctrine ORM is not able to establish that kind of mapping associations.
352
- To do that, the ORM RouteProvider follows the pattern of FQN:id. That is, the full
353
- model class name, then a colon, then the id. You only need to add it to the
354
- defaults parameters of the route with the ``RouteObjectInterface::CONTENT_ID ``
355
- key. ``cmf_routing.content_repository `` service can help you to do it easily.
356
- A new route can be created in PHP code as follows::
349
+ Symfony Cmf routing system allows us loading whatever content from a route. That
350
+ means an entity route can reference to different types of entities. But Doctrine
351
+ ORM is not able to establish that kind of mapping associations. To do that, the
352
+ ORM RouteProvider follows the pattern of `` FQN:id `` . That is, the full model
353
+ class name, then a colon, then the id. You only need to add it to the defaults
354
+ parameters of the route with the ``RouteObjectInterface::CONTENT_ID `` key.
355
+ ``cmf_routing.content_repository `` service can help you to do it easily. A new
356
+ route can be created in PHP code as follows::
357
357
358
358
// src/AppBundle/DataFixtures/ORM/LoadPostData.php
359
359
namespace AppBundle\DataFixtures\ORM;
0 commit comments