Well, the current 2.0 spec does not allow it. But the in-progress 3.0 spec does
> On Oct 15, 2016, at 10:20 AM, Michael Reed wrote:
>
> Thanks Tony Tam,
>
> Does that mean that the OpenAPI spec recommends not sending objects in the
> query? The alternative is to send two simple arrays where
Thanks Tony Tam,
Does that mean that the OpenAPI spec recommends not sending objects in
the query? The alternative is to send two simple arrays where one gives
the id values and the other gives the offset values, however, this approach
does not seem as intuitive for the user.
--
You received
Query parameters may not be complex types (type object).
> On Oct 15, 2016, at 9:40 AM, Michael Reed wrote:
>
> Hi,
>
> I wish c to look like [{id:123,offset:321}, {id:111,offset:222}, ...] but
> keep on getting the below error. How do I define an array of objects as a
&
Hi,
I wish c to look like [{id:123,offset:321}, {id:111,offset:222}, ...] but
keep on getting the below error. How do I define an array of objects as a
parameter? Thank you
parameters:
trendIDs:
name: 'c[]'
description: Requested trend point ID/offset pairs
in: quer
