reference in parameters is not compiled to md at all. about widdershins HOT 3 CLOSED

PS. This schema is pretty valid in swagger.

from widdershins.

Hi @astsiatsko I believe the problem is that your API definition only has a consumes of application/x-www-form-urlencoded, which means body parameters are sent as simple key:value pairs in the POST request, but with no information as to how that body parameter should be structured.

I would expect a body parameter to have a related consumes (at operation or root level) of `application/json', 'text/x-yaml', 'application/xml' or some other structured format.

Can you let me know if application/x-www-form-urlencoded really is the correct / working content-type for your POST request? There is a related PR (#15) but at the moment I am still unconvinced it is correct to merge that change.

Your Request definition is also missing a "type": "object" - if you add this and a structured consumes content-type, then the Request body parameter and all code-samples look correct to me.

from widdershins.

This is fixed in v2.0.2. The body parameters are handled in a different way, and the missing type: object in schema definitions is patched automatically.

from widdershins.