You don't want formData, you want an object, with attribute "sources" which is
type "array".
> On Sep 21, 2016, at 6:50 PM, Mathieu Pheulpin wrote:
>
> I'm trying to describe the following post parameter in swagger:
>
> {
> "sources": [
> {
>
I'm trying to describe the following post parameter in swagger:
{
"sources": [
{
"id": 101,
"parentId": 201
},{
"id": 102,
"parentId": 201
},{
"id": 102,
Done - https://github.com/swagger-api/swagger-ui/issues/2417
--
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 swagger-swaggersocket+unsubscr...@googlegroups.com.
For
Thanks, that's very useful.
I'm working on writing a validator now. Hopefully I should be able to open
source it in the next few days.
On Tuesday, September 20, 2016 at 5:23:50 PM UTC+1, tony tam wrote:
>
> Yes, there is a JSON schema to describe the swagger specification, and
> also the
Hi Ron,
I did it and wing328 solved the issue on the codegen project.
Kind regards.
2016-09-21 1:22 GMT+02:00 Ron Ratovsky :
> Hi Benjamin,
>
>
>
> We may have discussed this on IRC.
>
> Generally speaking, the ‘tags’ should affect the controller name.
>
> If you find that’s