fix: Clarify __invoke distinction

[botris]

When creating custom controllers the invoke method parameter name differs depending on the HTTP method.

[alanpoulain]

Are you sure it's the case? Where is the attribute set?

[botris]

When I have this entity:

/**
 * @ApiResource(
 *     itemOperations={
 *         "example_start": {
 *              "method": "GET",
 *              "path": "/example/start/{uuid}.{_format}",
 *              "controller": StartExampleController::class,
 *              "read": false,
 *          }
 *     },
 *     collectionOperations={}
 * )
 */
class Example
{
    /**
     * @ApiProperty(identifier=true)
     */
    private UuidInterface $uuid;

And I do this in my controller

public function __invoke($data): Response
{
//
}

I get: "Could not resolve argument $data of \"app\\controller\\startexamplecontroller()\", maybe you forgot to register the controller as a service or missed tagging it with the \"controller.service_arguments\"?"

But it works if I do

public function __invoke($uuid): Response
{
//
}

Which leads me to believe that the argument name must match the identifier name

[alanpoulain]

OK I see why now, it's because the route parameters are given directly to the controller method.
I've also added your change there #1390, thank you!

[guilliamxavier]

I think that's wrong: the cause was not (only) you using GET but "read": false

(I have used GET with $data, working)

[alanpoulain]

You can also retrieve the identifier even if read is true. But you are right, it should be modified to say that is also works for GET.

[alanpoulain]

See: #1392