[Routing] Add {foo:bar} syntax to define a mapping between a route parameter and its corresponding request attribute

[alamirault]

Fix #19846

[javiereguiluz]

Antoine, thanks for this contribution!

[rcsofttech85]

I did not find any example on map entity, you may consider this example below

    #[Route(path: '/profile/{name:name}/{age:age}', name: 'profile', methods: ['GET'])]
    public function fetchProfile(Profile $profile): Response
    {
       // 

    }

[alamirault]

I did not find any example on map entity, you may consider this example below

    #[Route(path: '/profile/{name:name}/{age:age}', name: 'profile', methods: ['GET'])]
    public function fetchProfile(Profile $profile): Response
    {
       // 

    }

I'm not sure to understand your suggestion, why map name to name and age to age ?

I think the original PR has no direct link with MapEntity ?

[rcsofttech85]

@alamirault The main idea was to improve automapping doctrine entities. Now, automapping of entities in favor of mapped route parameters is deprecated. The code I posted is a working example of entities and route parameters.

{name:name}/{age:age} = > "foo" is the name of the wildcard and "bar" is a property or attribute of the entity.

Here is another simple example:

    #[Route(path: '/product/{product_slug:slug}', name: 'product', methods: ['GET'])]
    public function getProduct(Product $product): Response
    {
       // 

    }

@nicolas-grekas could you please ensure it's correct.

[nicolas-grekas]

I think we need to be more precise. There are two steps between parameters and controllers:
The routing side does only one thing: populate a parameter named _route_mapping.
Then a listener will use that to map parameters to request attributes.
And then argument resolvers will map to controllers.
Explaining the steps can empower readers.
Not sure what exactly how we should say all this :)

[rcsofttech85]

Thanks for the info. I just wanted to help with the code which works with this new feature.. :)