-
Notifications
You must be signed in to change notification settings - Fork 14
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
OpenAPI 2.0 support #389
Labels
Comments
char0n
added a commit
that referenced
this issue
Nov 1, 2023
char0n
added a commit
that referenced
this issue
Nov 1, 2023
char0n
added a commit
to swagger-api/swagger-js
that referenced
this issue
Nov 1, 2023
ApiDOM@0.82.0 comes with parsing support of OpenAPI 2.0. The goal of this commit is to integrate the the ApiDOM line supporting OpenAPI 2.0 ASAP. Refs swagger-api/apidom#389
char0n
added a commit
to swagger-api/swagger-js
that referenced
this issue
Nov 1, 2023
ApiDOM@0.82.0 comes with parsing support of OpenAPI 2.0. The goal of this commit is to integrate the ApiDOM line that supports OpenAPI 2.0 ASAP. Refs swagger-api/apidom#389
char0n
added a commit
to swagger-api/swagger-editor
that referenced
this issue
Nov 1, 2023
char0n
added a commit
to swagger-api/swagger-editor
that referenced
this issue
Jan 23, 2024
char0n
added a commit
to swagger-api/swagger-editor
that referenced
this issue
Jan 23, 2024
Closing this. New issues related to enhancing OpenAPI 2.0 can be either attached to this closed epic or just live without an epic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal of this epic is to implement new namespace called
apidom-ns-openapi-2-0
. This namespace will implement OpenAPI 2.0 specification.The text was updated successfully, but these errors were encountered: