Add a decorator to change the name of a schema component name, instead of using the DTO name.

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

Being able to decouple the name of the schema component definition from the DTO name would be very helpful.

This is useful in organizations that use a large API where several teams contribute contracts that may include conflicting schema/component names. So instead of forcing devs to name their DTOs in a way that avoids conflicts, this would allow devs to use whatever name is desired for their DTOs but then override the published component name with something else.

Describe the solution you’d like

Perhaps something like @ApiModel({ name: 'NonConflictingComponentName }), or something similar.

This could be added to classes, like so:

@ApiModel({ name: 'TeamAExample' })
export class ExampleDto {
...
}

Which would produce:

  "components": {
    "schemas": {
      "TeamAExample": {}

Teachability, documentation, adoption, migration strategy

See above.

What is the motivation / use case for changing the behavior?

See above. Effectively, multi-tenant gateways that combine OpenAPI contracts together.

[adworacz]

I have not, unfortunately. My team is still blocked on seeing the PR merged. I might take a crack at creating a fresh PR soon if it looks like the current one has too many conflicts.

[felixhagspiel]

@adworacz it looks like #983 is still not merged. Have you found another solution for this?