Move to OpenAPI Generator #25
Assignees
Comments
slifty
added a commit
that referenced
this issue
May 22, 2024
The Swagger Codegen project was forked a few years back and the majority of the community moved over to the forked version [1]. This explains why we were facing some odd issues and a lack of support for the Open API specification 3.1 Moving to this more maintained version of the codegen project will immediately result in some bug fixes (specifically, `object` will be mapped to `object` instead of `any`). It will also allow us to use 3.1 in our api specification. Eventually this change may allow us to leverage community-defined typescript templates instead of our own custom templates. Issue #25 [1] https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been facing some issues with swagger codegen at the core library level (objects mapping to
any, and lack of support for 3.1)In looking for solutions, I've found that there is a much more active equivalent to swagger codegen: OpenAPI Generator. It looks like most of the community has moved into that project, and you can see a much more vibrant list of maintainers and commits!
It appears to be built from swagger codegen, so I don't think migration will be too tough?
https://github.com/OpenAPITools/openapi-generator/blob/master/docs/customization.md
The text was updated successfully, but these errors were encountered: