Why all ApiPlatform\OpenApi\Model are marked as final ?

[DeLm0re]

Hello guys,

I've been working with api version 3.1 for a while now which uses a nomenclature like this:

new Metadata\GetCollection(
    routeName: 'api_get_user',
    openapi: new Model\Operation(
        responses: [
            Response::HTTP_UNAUTHORIZED => new Model\Response(ResponseMessage::UNAUTHORIZED),
        ],
        parameters: [
            new Model\Parameter(
                name: 'id',
                in: 'query',
                description: 'The User identifier',
                schema: ['type' => 'object'],
                style: 'deepObject',
                explode: true,
            ),
            new Model\Parameter(
                name: 'name|lastname|username',
                in: 'query',
                description: 'The User denomination',
                schema: ['type' => 'object'],
                style: 'deepObject',
                explode: true,
            ),
        ],
    ),
),

As you can see, I always use, for my query parameters, deepObjects which will be sent to an internal code which will generate the queries for the database.

From the code snippet above, I looked for a simplified way by creating a personal Model\Parameter which already contains some properties like style, explode, schema et in. It would have prevented me from copy pasting the same code in each entity (these properties are always the same in all of my Metadata\GetCollection parameters and in each entities).

However, it seems like all Model are marked as final which makes my idea unfeasible.

I tried to create my own Model\DeepObjectParameter, identical to Model\Parameter, with the same getters/setters, without success (it does not seem to be recognized by openai).

So I was wondering why all these Model (Response, Parameter ...) were marked as final ?
Is this mandatory for api-platform/core ?
Isn't there a way to remove final and rely on an interface (considering that final was there to force a "type") ?

Thanks.

[DeLm0re]

Devs answer: it's because the openapi models follow the specification, they're not meant to be extended
if we allow so we'd have specification that will fail validation
I understand it's frustrating not being able to extend these models, you should probably just create your own OpenApiFactory that transforms every resource classes implementing a given interface
you can decorate ours

I'm closing the discussion