-
Notifications
You must be signed in to change notification settings - Fork 165
Supports OpenAPi spec v2.0 / v1.2 #53
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
Comments
Hello viclovsky, |
Yes, sounds good for me. It would be great if you make this task! Moreover, I will be able to do Maven plugin for easiest way for using your library in any project. I'll create separate ticket for that. |
@viclovsky i made a PR #53 to add the support but it seems there is a problem with |
This will be a big limitation of this approach: When parsing an old spec, you compare the result of the Swagger-Parser-Converter, which does an on the fly conversation to OAS3. I work a lot with the Parser (and the converter module) for the OpenAPI-Generator project and there are a lot corner cases that needs to be fixed... But it gets better and better (one issue at the time). |
Ok :) Thank you for your feedback @jmini ! |
Thanks a lot,
|
Your contract seems invalid.
|
|
Your contract isn't correctly designed. paths:
/some/api/method/{id}:
GET:
#...
DELETE:
#... |
is already reported as swagger-api/swagger-parser#755, will be fixed in the next version of Swagger-Parser. |
Yep, thanks a lot!! I've found swagger-api/swagger-editor#1677 ... Thus I'm planning to change my spec to fit it )) |
If you are interested, I have published an in-between release of Some v2-to-v3 conversions issues are fixed. |
Hello, is there any activity to support v2.0 Open API still or has this been abandoned? |
Hi @peterwa82, i can try again :) But last time, there was some issues in the project |
There may still be issues with it. I tried converting a 2.0 spec but noticed the required attribute of my query parameters was left null, which is wrong and results in a null pointer exception later. |
@peterwa82 you need to report the issue you get in the https://github.com/swagger-api/swagger-parser project. With a simple example (OpenAPI v2.0) as input and with your expectation if the OpenAPI v3 is not the one you are expecting. Here you will see a really simple java program to run swagger-parser independently: |
See screenshot |
Fixed in 7734db0. |
Thanks a lot for a great tool. I really want to use it in my projects but it is impossible because there is no support of older versions of OpenAPi spec: 1.2 and 2.0. Is there any plans to fix it?
The text was updated successfully, but these errors were encountered: