Closed youhangwang closed 6 years ago
Yes, downgrading to 2.0 will generally be lossy. There's nothing we can do for the lack of oneOf
support in 2.0
Can it please forcibly remove oneOf
under a path parameter? When trying to create an ApiConfig (OAS 2.0) for GCP API Gateway, it rejects the operation because oneOf
fails validation.
"Will generally be lossy", yes. But in this context, not lossy enough!
When I use
api-spec-converter --from=openapi_3 --to=swagger_2 --syntax json --order=alpha swagger.json > swagger2.0.json
, I found it cannot changeoneOf
(only support in 3.0) to a swagger 2.0 suitable format.