Mika Kunnas

I'm interested in this as well. I am currently writing specs with API Blueprint with the intent of generating JSON schemas from request bodies for validation purposes. The schema generation...

Good point! I'll deprecate this package as well. @philsturgeon (I believe) is maintaining [https://github.com/openapi-contrib](openapi-contrib) packages, so you might want to contact him. I'll update the deprecation warning and add a...

Oh. Didn't know that :smiley: Well, support for 2.0 is not tested or really even considered, so I would be inclined to document that it MAY support 2.0 but is...

Thanks for the differences, really helpful! So it should work otherwise except for the `type: "file"`. It throws because it's not one of the types defined in the OpenAPI 3.0...

`type: "file"` seems to be available only for `Parameter Object` and `Response Object`. The former can't be converted anyways (at least not yet) and the latter doesn't really represent a...

I can see your point and it certainly would make sense for requests. But the problem is that `type: "file"` is defined on the root of the [`Parameter Object`](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#parameter-object) rather...

I think the first step is to support OpenAPI 2.0 so that any `type: "file"` in a `Schema Object` is handled reasonably as this package was originally designed to handle...

This certainly makes sense and I understand your point now. The discussion and requested feature set has moved quite a bit away from the title of this issue which confused...

Thanks for the issues! It's probably better to leave this open although it might trick someone to believe that OpenAPI 2.0 is supported and not just documented. What comes to...

I agree and I was just thinking about the priority of "completing" OpenAPI 3.0 support vs adding OpenAPI 2.0 support. There might be flags that are relevant for OA 3.0,...