API Platform version(s) affected: 4.3.17
Description
Hi @soyuka
Because the OpenApiFactory does an explicit check on PATCH / PUT / POST,
|
\in_array($method, ['PATCH', 'PUT', 'POST'], true) |
an operation which does DELETE never have a request body generated.
This is often ok since DELETE does not require a request body. But for custom DELETE which are using Inputs, documentation would be nice.
I wonder if this was done on purpose or if this should be fixed ?
How to reproduce
new Delete(
uriTemplate: '/foo/bulk-delete',
status: 200,
openapi: new Operation(
responses: [
200 => new Response(description: 'Foo deleted successfully'),
],
),
input: BulkInput::class,
output: BulkOutput::class,
read: false,
deserialize: true,
processor: BulkProcessor::class,
),
with
class BulkInput
{
/**
* @var Uuid[]
*/
public array $uuids = [];
//...
}
The uuids field is not documented.
API Platform version(s) affected: 4.3.17
Description
Hi @soyuka
Because the OpenApiFactory does an explicit check on PATCH / PUT / POST,
core/src/OpenApi/Factory/OpenApiFactory.php
Line 473 in dd00d0f
an operation which does DELETE never have a request body generated.
This is often ok since DELETE does not require a request body. But for custom DELETE which are using Inputs, documentation would be nice.
I wonder if this was done on purpose or if this should be fixed ?
How to reproduce
with
The
uuidsfield is not documented.