Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abstract away from OpenAPI via transformation. #843

Open
jimschubert opened this issue Aug 18, 2018 · 0 comments
Open

Abstract away from OpenAPI via transformation. #843

jimschubert opened this issue Aug 18, 2018 · 0 comments

Comments

@jimschubert
Copy link
Member

Description

We have abstractions such as CodegenModel, CodegenOperation, CodegenProperty, etc. which represent abstractions away from OpenAPI for the sake of generation. This currently creates tight coupling between different versions of OpenAPI specifications and the underlying templating (examples: CodegenOperation#vendorExtensions, CodegenOperation#externalDocs)

Suggest a fix/enhancement

Create a representation of an API which is not tightly bound to OpenAPI specifications in general. Transform from OpenAPI specification to this data type via transform phase and inject this transform into the workflow (either DefaultGenerator or Executor (tbd #841).

This will unblock us to eventually allow configurable input specification parsers as well as configurable transforms (effectively opening us to code generation for all specification formats).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant