For now, that’s not a limitation of the tool but the spec. For the 3.0 specification, support for this has been / is being added. Not much longer now…
> On Nov 18, 2016, at 6:25 AM, Scott Schafer <[email protected]> wrote: > > We have APIs that take multiple parameters, some of which are string-encoded > JSON objects that are passed in the form data. > > I've had to resort to writing descriptions like: > > "string-encoded map of field names to booleans, example: {status: true, > selectedProposal: true, notes: true, oppDataEntry: true}" > > But this breaks down with complex objects. How can we document their format? > Is there a way to do this? Can I at least put a link to the definition in the > description? > > -- > 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.
