Ron

The solution should be simple. As far as I understand, the paths listed in the resource listing (that is, the api-docs) all have a `.{format}` extension and the api declarations...

Okay, but keep in mind I'm talking about the actual API operations but rather the the Swagger documentation endpoints produced by grape-swagger.

Wish I could help there, unfortunately my knowledge of ruby ends with about recognizing the file extension.

@myok12 that's an interesting idea. @frantuma do you have any thoughts on the suggestion?

@antihax, @bvwells - your input would be appreciated.

OAS2 indeed doesn't support `null` values directly. OAS3 - does, using the `nullable` property.

It's an interesting situation. Sway, as far as I understand, allows you to provide custom code validations (and uses some of its own), but at the core uses a JSON...

@whitlockjc I believe they *are* using vendor extensions, they're just using a modified json schema to validate their own vendor extensions. Azure specs are by all means valid Swagger specs...

Looks like this breaks the build (because of openjdk11) - can you please take a look?

Fixed: - Parameters reference components now. - Top level body and formData parameters are converted to request bodies. Not fixed: - Path level formData and body parameters are not converted....