@Schema(name="Car")
data class Car1(val p1: String)
@Schema(name="Car")
data class Car2(val p2: String)
This will today generate a single Car schema in the openapi spec (while it seems not deterministic which of both types will be used). So one type is missing in the spec. The generated spec is valid and the generator process finishes with status ok, without any hint that some Schemas were overridden.
A similar issue was solved with #947 . But that fix only considers the name of the type and not the annotated Schema.name override.
It would be good to either:
Generate underscore suffix (as done in #947) based on the Schema.name
Have a configuration property to make the process error if overrides would happen
Feature description
Consider this situation
This will today generate a single Car schema in the openapi spec (while it seems not deterministic which of both types will be used). So one type is missing in the spec. The generated spec is valid and the generator process finishes with status ok, without any hint that some Schemas were overridden.
A similar issue was solved with #947 . But that fix only considers the name of the type and not the annotated Schema.name override.
It would be good to either: