-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Migrating from Swagger 2.0 to OpenAPI 3.0 #447
Comments
Hey @Paul-vrn . Thanks for the initiative and the collaborative spirit. I am sorry to redirect you to #442 There is little use for yet another abandoned pull-request unless the project is rebooted, and that seems unfeasible. For all it's worth, just keep those improvements in your fork and announce that in #375 / #399 |
@Paul-vrn Hi, could you please share Open Api 3.0 specification? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wanted to migrate the Swagger 2.0 specification of the project to OpenAPI 3.0 to achieve better compatibility with OpenAPI code generators and to keep the project up-to-date with the latest standards.
Additionally, for personal needs, I have already recreated and corrected the specification in OpenAPI 3.0 to accurately reflect the response payloads and match the actual behavior of the API requests.
So if it's ok, I can open a pull request 🙂
The text was updated successfully, but these errors were encountered: