[HttpKernel] Map a list of items with MapRequestPayload attribute

[yceruto]

Q	A
Branch?	7.1
Bug fix?	no
New feature?	yes
Deprecations?	no
Issues	-
License	MIT

Request:

Content-Type: application/json
[
    {"price": 50},
    {"price": 23}
]

Controller:

class MyController
{
    public function __invoke(
        #[MapRequestPayload(type: Price::class)] array $prices,
    ): Response {
        // do something with $prices -> array<Price>
    }
}

Cheers!

[smnandre]

Couple of questions there:

• Would this work with forms, or XML ?
• Does the validation still work ?

[yceruto]

Couple of questions there:
Would this work with forms, or XML ?

The feature behind this improvement is completely agnostic to the request format. It will work with any data format supported by the Serializer component. See more here: https://symfony.com/doc/current/components/serializer.html#handling-arrays

Does the validation still work ?

Yes, the validator component does support any iterable value.

[smnandre]

I did not see how a form could send data as flat array at first... hence my question. But i'm indeed not aware of all the possibilties offered by the serializer there.

(for the validation i was referring to the validationGroups attribute.. just to know how this would compare to the nested array of DTOs for instance)

[yceruto]

(for the validation i was referring to the validationGroups attribute.. just to know how this would compare to the nested array of DTOs for instance)

If set, it will be applied to each element of the collection as implemented here:

symfony/src/Symfony/Component/Validator/Validator/RecursiveContextualValidator.php

Line 332 in 78c6ceb

private function validateEachObjectIn(iterable $collection, string $propertyPath, array $groups, ExecutionContextInterface $context): void

[chalasr]

At some point, the new TypeInfo component could certainly help guessing what $type is (when possible)

[chalasr]

Nice one. Thanks Yonel!