-
Couldn't load subscription status.
- Fork 9
feat: add Swagger 2.0 support with upgrade to OpenAPI 3.0 utility #66
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
Conversation
… /paths and top-level security; remove unused top-level tags; update docs
…d circular reachability test
📊 Test Coverage ReportCurrent Coverage: Coverage Change: 📉 -1.0% (decreased) Coverage by Package
📋 Detailed Coverage by Function (click to expand)
Generated by GitHub Actions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a couple of minor issues.
I didn't go into detail reading all the swagger types or the tests, but I assume the tests should cover that stuff pretty well.
Add Swagger 2.0 Support with OpenAPI 3.0 Upgrade Utility
This PR adds comprehensive support for Swagger 2.0 specifications including full parsing, validation, walking, and an upgrade utility to convert to OpenAPI 3.0.
Changes
Swagger 2.0 Support
Upgrade Utility
swagger: "2.0"→openapi: "3.0.0"host/basePath/schemes→serversdefinitions→components.schemasparameters(body) →components.requestBodiessecurityDefinitions→components.securitySchemescontentobjects#/definitions/→#/components/schemas/)CLI Commands
openapi swagger upgrade- Convert Swagger 2.0 to OpenAPI 3.0openapi swagger validate- Validate Swagger 2.0 documentsAdditional Improvements
\u0000) instead of Go-style hex escapes (\x00)t.Context()for better lifecycle managementTesting
Breaking Changes
None - this is purely additive functionality.