json-schema definition for parameters

[mbroadst]

It doesn't seem possible to describe the parameters of an endpoint with plain json-schema, which I find curious. One can use json-schema to define a named parameter (parameters: { thing: { in: 'body', schema: { $ref: '....' } }), but not for the entire definition - which seems restrictive. This essentially introduces two acceptable schema formats, and a far less flexible one at that (in the case of the non json-schema format). The only way I can think of doing this is to basically add a top level dummy key (e.g. data) that then uses my json-schema.

So I guess my question is: are there any plans in the future to support parameter definitions in plain json-schema?

[mbroadst]

Ah it looks like this was handled over here: #670

apologies for the noise

[ePaul]

@mbroadst I think it was changed in #654 instead.

Though I'm not sure I understood what you actually wanted. Please note that the "schema" objects API definitions are not exactly the same as JSON schema objects (though there is some overlap, and many objects fulfill both specifications).