-
Notifications
You must be signed in to change notification settings - 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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… /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 |
BlakeTheAwesome
suggested changes
Oct 17, 2025
Contributor
BlakeTheAwesome
left a comment
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.
BlakeTheAwesome
approved these changes
Oct 17, 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
marshalling
Related to data marshalling/unmarshalling
openapi
Related to OpenAPI core functionality
tests
Test-related changes and improvements
tooling
Development tools and utilities
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.