schemaMapping configuration to re-use existing model classes

[rquinio1A]

Why do we need this improvement?

With openapi-generator we're relying on the schema-mapping feature.
Would it be possible to have a similar feature built-in modelina ?

How will this change help?

schema-mapping allows to re-use some existing model objects instead of generating them.
This allows us to build helpers or utilities that can be shared across several APIs built around shared types.

Screenshots

No response

How could it be implemented/designed?

Maybe re-using the design from https://openapi-generator.tech/docs/customization/#schema-mapping

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

No, someone else can work on it.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jonaslagoni]

So basically, if the model is about to be generated, check it against schemaMapping, and if the names match use that mapping value instead?

Would it need to handle dependencies, i.e. you would like to also import the type? Or do you always assume that whatever the mapping value is is taken as is?

[rquinio1A]

So basically, if the model is about to be generated, check it against schemaMapping, and if the names match use that mapping value instead?
Would it need to handle dependencies, i.e. you would like to also import the type?

Exactly, if there's a schema mapping for a referenced type, do not generate it and reference the existing one instead.
In Java jaxrs-spec generator I know it uses the inline (fully qualified) type, without an import, but I guess it may be language/template-specific.

<schemaMappings>
    <schemaMapping>Error=com.acme.Error</schemaMapping>
</schemaMappings>

private @Valid List<com.acme.Error> errors;

[jonaslagoni]

Alright, yea I think it makes sense to add something like this 👍