swagger-api / swagger-api/swagger-codegen
Support OpenAPI 3.1.0 Specification in Swagger Codegen
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi team,
Firstly, thank you for your great work on maintaining Swagger Codegen!
I'm reaching out to request support for OpenAPI 3.1.0 in swagger-codegen. Currently, the latest stable version of the tool supports OpenAPI 3.0, but we are using features specific to OpenAPI 3.1 (like jsonSchemaDialect, oneOf/anyOf enhancements, and $schema) which are not yet supported.
Why it's important:
OpenAPI 3.1.0 aligns more closely with JSON Schema draft 2020-12.
This will enable better type generation and schema reuse across languages.
Use Case:
We're generating client SDKs from an OpenAPI 3.1 spec and facing compatibility issues or generation failures.
Request:
Please consider adding OpenAPI 3.1.0 support to swagger-codegen, or let us know if there are any workarounds or ongoing plans.
Thank you for your time and support!
Raghu
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by examining the existing OpenAPI 3.0 parsing and generation path, then reproduce the reported failures with jsonSchemaDialect, $schema, and oneOf/anyOf inputs. Done means defining and implementing a decided scope for OpenAPI 3.1.0 support and confirming client SDK generation works for those features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100