Open msillence opened 5 years ago
+1
I think this feature request should log in the Swagger Parser repo instead as OpenAPI Generator relies on Swagger Parser to parse the spec at the moment.
@wing328 what exacly swagger parser is used? https://github.com/OpenAPITools/swagger-parser or https://github.com/swagger-api/swagger-parser ?
https://github.com/swagger-api/swagger-parser
(We filed some PRs to https://github.com/swagger-api/swagger-parser before and since it took some time to review, we were using https://github.com/OpenAPITools/swagger-parser before those PRs got merged)
+1, would it make sense to provide a config for all other schemas too? Meaning request, response, ... schemas?
Any news?
Any update on this?
also pinging this issue for an update plz && ty
Is your feature request related to a problem? Please describe.
We have services in two places that include the same domain objects We want to generate all the domain objects even if we don't have a service definition that uses them
Describe the solution you'd like
We slit out our service and domain definitions generating all the domain objects not not necessarily all the service definitions we use the $ref to refer to the definitions in the other file
$ref: 'domain-core.yaml#/components/schemas/DomainObject
we'd like to be able to generate all the domain objects in that other file
Describe alternatives you've considered
We are considering generating a dummy service file that references all objects
Additional context
Our domain objects and services are used in multiple systems we'd like a single source of these domain objects even if they are only used internally by some systems or exposed in a different way to our main services.