Yes, this is not supported in the 2.0 Swagger specification. It will be in the 3.0 Open API spec but for now, your only option is to use a string.
> On Jul 13, 2016, at 2:58 PM, Parag Baxi <[email protected]> wrote: > > Tried SO first. > <http://stackoverflow.com/questions/38342488/how-to-document-swagger-query-parameter-with-json-object-input> > > How do I define a JSON object value for a request parameter that is in: query > (not in: body)? > > Example below: > > paths: > /schedules: > get: > summary: Gets the list of schedules > description: | > The schedules endpoint returns information about the configured > schedules. > parameters: > - name: filter > in: query > description: > > Returns whether alert runs on matching schedule. > > > Example request: > > > { > "type": "a", > "start" : "b", > "stop" : "c" > } > required: true > type: string > Because it's not in: body, I cannot use schema. > > > > -- > You received this message because you are subscribed to the Google Groups > "Swagger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
