Mechanism for handling duplicate component class names

[peterbrostl1979]

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

This feature request stems from my problem with a large json where the method parameters share the same class name but have different ancestor paths like.

• "$ref": "#/components/schemas/RootNamespace.Contracts.FunctionalityOne.InputType"
• "$ref": "#/components/schemas/RootNamespace.Contracts.FunctionalityTwo.InputType"
• "$ref": "#/components/schemas/RootNamespace.Contracts.FunctionalityThree.InputType"
• ...

This results in classes being generated with names InputType, InputType1, InputType2,...

Describe the solution you'd like

I can imagine two possible solutions, either to have an option to prefix the class name with their ancestor(s) or introduce a custom attribute in the schema definition indicating the target class name somehow (not sure if openapi allows that however)

Describe alternatives you've considered

The cleanest alternative would be to fix the json here, however that is not (easily) possible in all situations