@@ -418,14 +418,14 @@ The example in this section applies if you use the ORM route provider
418
418
``staticPrefix `` field of the
419
419
``Symfony\Cmf\Bundle\RoutingBundle\Doctrine\Orm\Route `` to find route candidates.
420
420
421
- Symfony Cmf routing system allows us loading whatever content from a route.
422
- That means an entity route can reference to different types of entities.
423
- But Doctrine ORM is not able to establish that kind of mapping associations.
424
- To do that, the ORM RouteProvider follows the pattern of FQN:id. That is, the full
425
- model class name, then a colon, then the id. You only need to add it to the
426
- defaults parameters of the route with the ``RouteObjectInterface::CONTENT_ID ``
427
- key. ``cmf_routing.content_repository `` service can help you to do it easily.
428
- A new route can be created in PHP code as follows::
421
+ Symfony Cmf routing system allows us loading whatever content from a route. That
422
+ means an entity route can reference to different types of entities. But Doctrine
423
+ ORM is not able to establish that kind of mapping associations. To do that, the
424
+ ORM RouteProvider follows the pattern of `` FQN:id `` . That is, the full model
425
+ class name, then a colon, then the id. You only need to add it to the defaults
426
+ parameters of the route with the ``RouteObjectInterface::CONTENT_ID `` key.
427
+ ``cmf_routing.content_repository `` service can help you to do it easily. A new
428
+ route can be created in PHP code as follows::
429
429
430
430
// src/AppBundle/DataFixtures/ORM/LoadPostData.php
431
431
namespace AppBundle\DataFixtures\ORM;
0 commit comments