About the updated form array in v1.7.5

[xuerbujia]

When I Declaer

var v struct {
Codes []string form:"Codes"
}
If a code is comma separated like aaa,bbb,ccc. When I enter parameter ? codes=aaa,bbb,ccc&codes=ccc,ddd,eeeIt is normal but when I enter only one ? codes=aaa,bbb,ccc And it blew up.
So I think we should use the tag to turn this comma-separated array parsing on or off

[xuerbujia]

I can post a PR if it have to

[kevwan]

on codes=aaa,bbb,ccc, it will be splitted as ["aaa", "bbb", "ccc"].

This is not what you want?

[xuerbujia]

on codes=aaa,bbb,ccc, it will be splitted as ["aaa", "bbb", "ccc"].

This is not what you want?

"aaa,bbb,ccc" is a key.My param is a array of the key, and it gets wrong split when I input in only one

[kevwan]

check it out here: https://stackoverflow.com/a/9547490

[xuerbujia]

Most of the discussion in this link is? a[]=1&a[]=2 or? a=1&a=2 .These two are fine as the default enable mode but the comma separation has the above bad case. I think there needs to be a way for the user to choose to enable or disable the one through the tag.

[xuerbujia]

code="aaa,bbb,ccc" is a key.
On the same API：
/path?codes=aaa,bbb,ccc&codes=ccc,ddd,eee --> []string{"aaa,bbb,ccc","ccc,ddd,eee"} Fine
path?code=aaa,bbb,ccc --> []string{"aaa","bbb","ccc"} bad. Because in this api the code(aaa,bbb,ccc) is a key.

[kevwan]

I can post a PR if it have to

OK, thanks for your contribution!