It should be fairly feasible to add support for OpenAPI 3 as swagger-to uses an intermediate layer. While we couldn't support all the features of OpenAPI 3, we could at least covert the overlap in features between Swagger (OpenAPI 2) and OpenAPI 3.
@falzm I suppose you would be interested in this feature? I would need a bit of help. While I can do the coding, I would need somebody to review the code (at least skim over it) and help me convert the specs in the unit tests from Swagger to OpenAPI 3. Would you have time and energy for that in the foreseeable future? I don't expect the effort to be huge.
It should be fairly feasible to add support for OpenAPI 3 as swagger-to uses an intermediate layer. While we couldn't support all the features of OpenAPI 3, we could at least covert the overlap in features between Swagger (OpenAPI 2) and OpenAPI 3.
@falzm I suppose you would be interested in this feature? I would need a bit of help. While I can do the coding, I would need somebody to review the code (at least skim over it) and help me convert the specs in the unit tests from Swagger to OpenAPI 3. Would you have time and energy for that in the foreseeable future? I don't expect the effort to be huge.