Skip to content

swagger 3.1 support #251

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

Open
hauner opened this issue Mar 29, 2025 · 2 comments
Open

swagger 3.1 support #251

hauner opened this issue Mar 29, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@hauner
Copy link
Member

hauner commented Mar 29, 2025

support OpenAPI 3.1 with swagger parser

@hauner
Copy link
Member Author

hauner commented Mar 30, 2025

the swagger parser does resolve 3.1 $refs differently than the 3.0 $refs when the resolve option is set. While 3.0 replaces external $refs with internal refs, 3.1 does inline the $ref. That is bad because it looses the "Name" of the $ref which is used/needed to generate (nice) class names.

Resolving $refs manually is too complicated with the swagger parser.

OpenAPI 3.1 will only be possible using the internal OpenAPI parser.

@hauner
Copy link
Member Author

hauner commented Mar 30, 2025

@hauner hauner added the enhancement New feature or request label Mar 31, 2025
hauner added a commit that referenced this issue Apr 2, 2025
hauner added a commit that referenced this issue Apr 2, 2025
hauner added a commit that referenced this issue Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant