Array parameter in path

[ghost]

Prerequisites:

type args struct {
    Id   []int64 `path:"id" validate:"dive,required" explode:"1"`
}

fizz.GET("/:id", []fizz.OperationOption{/*...*//}, tonic.Handler(func(ctx *gin.Context, args *args) error {
  fmt.Println(args)
  return nil
}, 200))

Then, when I make a request: curl "http://localhost:8080/1,2,3", I get error: binding error on field 'Id' of type 'args': strconv.ParseInt: parsing "1,2,3": invalid syntax.

[wI2L]

This is a question related to https://github.com/loopfz/gadgeto

See https://swagger.io/docs/specification/serialization/ Query parameters section, and https://github.com/loopfz/gadgeto/blob/66acbcfcb7e86d7d226e759d3609866a3dd11365/tonic/tonic_test.go#L90 for reference.

You are using the explode flag the wrong way.
The issue, specifically with your example is that you are trying to explode a value of a path parameter, but this isn't supported, it is only for query parameters.
Also, the meaning of explode:"true" is to indicate that the query parameters are represented as ?a=1&a=2&a=3, where a is your query parameter, and 1,2,3 the values. If explode is false, then the query sent should look like this: ?a=1,2,3.

[ghost]

It also not work with explode:"false". In specification array in path allowed.
So, I write an issue in https://github.com/loopfz/gadgeto

[wI2L]

The issue isn't related to the OpenAPI spec, nor the Fizz generator, but rather the lack of support for the explode feature of path parameters in tonic. Le ven. 6 sept. 2019 à 15:04, Виктор <[email protected]> a écrit :

…

It also not work with explode:"false". In specification array in path allowed. So, I write an issue in https://github.com/loopfz/gadgeto — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#34?email_source=notifications&email_token=ABRXWEKPKHQJ34QZFZMCCCTQIJIOHA5CNFSM4IUIOJXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6CY4NY#issuecomment-528846391>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABRXWEKJWRWCL2XRHHCQFQ3QIJIOHANCNFSM4IUIOJXA> .

[wI2L]

For reference, the path parameters extraction function can be found here.
It doesn't support the ExplodeTag tag, as the extractQuery function does.

[wI2L]

@ViktorPegy see loopfz/gadgeto#63, a PR has started to address what we talked about.