feat(symfony): ApiOperation attribute on controllers by soyuka · Pull Request #8628 · api-platform/core

soyuka · 2026-10-01T19:34:47Z

Q	A
Branch?	main
Tickets	#1423
License	MIT

#[Route('/orders/checkout', name: 'order_checkout', methods: ['POST'])]
#[ApiOperation(new Post(input: CheckoutInput::class, output: CheckoutOutput::class))]
public function __invoke(CheckoutInput $data): CheckoutOutput

operation flags (read, deserialize, validate, security, serialize, write) toggle the stages
controllers tagged controller.service_arguments are scanned at compile time, the resource class is class ?? output ?? input and becomes a resource if it isn't one already
the route name comes from the method's #[Route] (or routeName on the operation), uriTemplate is forbidden
works with and without use_symfony_listeners, stage defaults extracted from MainController into OperationStageDefaults
Laravel: follow-up

Run the API Platform pipeline (read, deserialize, validate, security, serialize, respond) on a plain Symfony controller route and document the operation in OpenAPI and Hydra. The route owns the path, the operation reuses it through routeName.

- resource class is class ?? output, input alone throws - dedicated name collection factory for controller resources - GET/GetCollection default to read: false - cover get, getcollection, patch and delete in jsonld/json/csv