Wrong query serialialization of defaultParams

Hey, thanks for a great lib, I found that query serialization is broken at least with defaultParams if empty arrays are presented. here is the object I use:

defaultParams: {
        a: 'string',
        b: [],
        c: [],
        d: [1, 2],
      }

and I’m getting following query ?a=string&&&d=1&d=2 as you might see there is additional & symbols for removed empty params. It getting worse after reload, because in this case route cant parse this query string correctly.

[Reaverart]

Just a thought about tricky moment here, without brackets we cant be sure when foo=bar is a { foo: bar } or if it a { foo: ['bar'] }, so maybe we need a configuration option? to serialize arrays in more explicit way, foo[]=bar or foo[0]=bar? hmm, a link to consider https://github.com/sindresorhus/query-string#arrayformat-1

[Reaverart]

Hi, @troch I was thinking about this issue, the way you mention in last comment isnt really suitable for me because params might change. But what if route config will accept custom parse / serialize (encode / decode) function? Then we will have flexible way to control query params on our own, anyone will be able to take any 3rd party lib he like for parsing/serialization queries or wrtite something specific when needed. Or maybe there is middleware for that?