Supports OpenAPi spec v2.0 / v1.2

[viclovsky]

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?

[quen2404]

Hello viclovsky,
this is not currently scheduled but you can create a merge request if you need it quickly.
Else, i will try to do this by the end of week, but i'm not sure if i will have enough time to do that. And after, it's my holiday during two weeks.

[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.

[quen2404]

@viclovsky i made a PR #53 to add the support but it seems there is a problem with swagger-parser-v2-converter.
I opened an issue in this project.
But you can already try to use it if you checkout the branch feature/support-swagger2

[jmini]

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).

[quen2404]

Ok :) Thank you for your feedback @jmini !

[viclovsky]

Thanks a lot,
Yep, I have already tried it but sounds like I have some problems with it: it fails cause it can't translate my v2.0 spec into v3.0. Converter fails => diff fails.

1. java.lang.IllegalArgumentException: Two path items have the same signature: /some/api/method/{}
   But I don't have such signature at all!!! I have /some/api/method/{id}, /some/api/method/{searchId}, /some/api/method/{id}/email
2. java.lang.NullPointerException
   at io.swagger.v3.parser.converter.SwaggerConverter.convert(SwaggerConverter.java:422)
   If there is no 'info' in specification

[quen2404]

Your contract seems invalid.

1. /some/api/method/{id} & /some/api/method/{searchId} is the same rest endpoint.
2. According to specification, info is required

[viclovsky]

1. Yep, /some/api/method/{id} & /some/api/method/{searchId} is the same rest endpoint, but they have different methods. First GET, second DELETE.
2. It was my fault — never mind

[quen2404]

Your contract isn't correctly designed.
You should have one path with two operations:

paths:
  /some/api/method/{id}:
    GET:
      #...
    DELETE:
      #...