-
Notifications
You must be signed in to change notification settings - Fork 20
OpenAPI 3.1.x support #546
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 3.1.x support #546
Conversation
|
OAS 3.x single class implementation |
|
This pull request has been automatically marked as stale because it has not had activity in the last 2 weeks. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
Please review this PR |
|
What is the current status of the review? |
|
This pull request has been automatically marked as stale because it has not had activity in the last 2 weeks. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
#553 OpenAPI 3.1 is needed because API-Manager supports this version and currently apim-cli is not able to handle it. |
|
Please look at this feature, this would help our dev teams immensely, right now we need to do a workaround in stoplight to make our oas specs 3.0.x |
|
Sonarcloud token seems to be invalid / missing,
Both these actions had the same error. The current one and this one. |
930e850
into
Axway-API-Management-Plus:develop
|
@o0-C-L-K-0o I have merged the changes, will test it as part of develop branch. |
|
@o0-C-L-K-0o sonar cloud test is passed. I will test the integration later along with other fixes. |
Issue #537
Merged parts of #542 into existing OAS implementation
Additional test with openapi 3.1 added