You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I happen to come across a peculiar situation where it made sense to leverage the "--type-mapping" feature as the requirement had external model dependencies. However it seems that this feature is non-compliant with standard OpenAPI spec
for example:
I pass typeMappings.set([ 'refType': 'com.package' ]) and then in spec.yml I would simply say type: refType
If I were to run this spec for creating swagger-ui it would cause an error like "undefined type".
Lucky for us spring-doc auto-config scans packages and generates swagger on the fly without the need to refer to the actual spec.yml
The caveat is that the generator doesn't map all essential sections of OpenAPI (i.e. info, tags, servers etc) to the camel REST-DSL. Which causes inconsistencies on swagger-ui.
Describe the solution you'd like
Update the java-camel generator to map essential sections of OpenAPI (i.e. info, tags, servers etc) to the camel REST-DSL if they're present.
OR
Provide a convenient way for the developer to configure these sections
Describe alternatives you've considered
Abstained from using "typeMapping" and reverted to traditional $ref
Additional context
It would enable flexible usage of generator specific features like typeMapping, schemaMapping without impacting swagger-ui concerns
This feature would improve swagger documentation with REST-DSL coming from the generator
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I happen to come across a peculiar situation where it made sense to leverage the "--type-mapping" feature as the requirement had external model dependencies. However it seems that this feature is non-compliant with standard OpenAPI spec
for example:
I pass typeMappings.set([ 'refType': 'com.package' ]) and then in spec.yml I would simply say type: refType
If I were to run this spec for creating swagger-ui it would cause an error like "undefined type".
Lucky for us spring-doc auto-config scans packages and generates swagger on the fly without the need to refer to the actual spec.yml
The caveat is that the generator doesn't map all essential sections of OpenAPI (i.e. info, tags, servers etc) to the camel REST-DSL. Which causes inconsistencies on swagger-ui.
Describe the solution you'd like
Update the java-camel generator to map essential sections of OpenAPI (i.e. info, tags, servers etc) to the camel REST-DSL if they're present.
OR
Provide a convenient way for the developer to configure these sections
Describe alternatives you've considered
Abstained from using "typeMapping" and reverted to traditional $ref
Additional context
The text was updated successfully, but these errors were encountered: