feat(swagger): Add OpenAPI v3 conversion to update_swagger.sh - #201
feat(swagger): Add OpenAPI v3 conversion to update_swagger.sh#201rahulsunil2 wants to merge 1 commit into
Conversation
Sorry, something went wrong.
Add functionality to convert Swagger 2.0 (OpenAPI v2) to OpenAPI v3 using api-spec-converter. The script now checks for the existence of the output directory and creates it if necessary. It also provides appropriate error handling and user feedback for the conversion process. This change enhances the API documentation workflow by providing up-to-date OpenAPI v3 specifications.
|
This PR has had no human activity for 90 days, so it has been marked lifecycle/stale. This is automated backlog grooming, not a judgment on the work. What happens next, unless there is activity:
To keep it open, push a commit or leave a comment, and the clock will reset. For work that should not auto-close, such as an RFC or long-running experiment, ask a maintainer to add lifecycle/frozen. |
Sorry, something went wrong.
|
This PR has had no human activity for 30 days since being marked lifecycle/stale, so it has now been marked lifecycle/closing-soon. It will be closed in 30 days unless there is new activity. If the work still matters, this is the moment to say so: leave a comment, push a commit, or ask a maintainer to add lifecycle/frozen if it should be kept open long-term. If this work is no longer being pursued, no action is needed. |
Sorry, something went wrong.
This PR adds functionality to convert Swagger 2.0 (OpenAPI v2) to OpenAPI v3 using api-spec-converter in the update_swagger.sh script.
Description
This PR enhances the update_swagger.sh script by adding the following features:
These changes improve the API documentation workflow by providing up-to-date OpenAPI v3 specifications alongside the existing Swagger 2.0 documentation.
References
Review Checklist