Default name for nested classes should include their parent class

[DeMol-EE]

We use a lot of nested classes: things like Type, Filters or Status. When the OpenAPI file is generated, it will do a best-effort to generate a unique name for each schema element. From what I understand, it currently just takes the class name, and resolves collisions by adding an incremental suffix. For example, Foo.Status and Bar.Status will result in Status1 and Status2.

Could the spec be augmented to require that nested classes include the name of their parent class in their generated default name? (For the example, this would yield FooStatus and BarStatus.)

[MikeEdgar]

This is reasonable behavior to expect, but probably not something we should make a part of the specification. The current spec doesn't have an opinion on how schema names are determined, aside from when they are explicitly given in @Schema(name = "...") or other similar places.

This would better be something that is an implementation features. Based on the naming behavior you describe, are you using a platform that incorporates smallrye-open-api [1]? If so, please consider opening a feature request there about this. It could likely be something that is added via a configuration option, perhaps.

[1] https://github.com/smallrye/smallrye-open-api

[DeMol-EE]

Oh, sorry, I thought the default in case no explicit name was given was also defined by the spec. Thanks for the advice, but I generally prefer not to rely on implementation-specific features, so I think I'll just start adding @Schema explicitly to all our inner classes.