feat(metadata) Customize Resource & operations

[loic425]

Q	A
Branch?	main
Tickets
License	MIT
Doc PR	api-platform/docs#...

The idea of this feature is to allow customizing built-in endpoints from a third party API (ex Sylius E-commerce API).

<?php

namespace App\Mutator;

use ApiPlatform\Metadata\AsResourceMutator;
use ApiPlatform\Metadata\ApiResource;
use App\Entity\Speaker;

#[AsResourceMutator(resourceClass: Speaker::class)]
final class SpeakerResourceMutator
{
    public function __invoke(ApiResource $resource): ApiResource
    {
        $operations = $resource->getOperations();
        $operations->remove('_api_Speaker_get_collection');

        return $resource->withOperations($operations);
    }
}

[soyuka]

Really cool, this is a follow up for php configured metadata as this allows to mutate vendor operations. I'll probably demonstrate this shortly.

I'd recommend to add a ResourceMutatorInterface. Obviously we should introduce an AsOperationMutator. I'd suggest that it takes:

public readonly string $operationName

URI Template would be nice as well but it will probably match several operations, therefore it's probably better to just use the $operationName.

[soyuka]

Suggested change

	final class CustomResourceMetadataCollectionFactory implements ResourceMetadataCollectionFactoryInterface
	final class MutatorResourceMetadataCollectionFactory implements ResourceMetadataCollectionFactoryInterface

[soyuka]

an interface would be able for typehint to know what the callable arguments are and make the code a little bit cleaner