Add support for alternative query parameter encodings (e.g. qs)

[wkelly1]

We are keen to move to using Nuqs but at the moment it looks like it does not fully support the qs query string format. As far as I can tell, it is not possible to use this format for both nested dynamic objects and arrays within Nuqs.

The closest workaround, provided you know the properties ahead of time, seems to be to use useQueryStates (as discussed here). In an ideal world, it would be possible to create a parser that was able to serialise and parse from a single value to multiple query parameters.

For example:

const exampleArray = ["a", "b", "c"]

which would result in

?exampleArray[0]=a&?exampleArray[1]=b&?exampleArray[2]=c

and something similar too for nested objects.

I appreciate that it may not be straightforward to extend the createParser options or logic to support this.

With that in mind, would it be worth considering an enhancement to the Adapter logic to allow overriding the following implementation?
https://github.com/47ng/nuqs/blob/next/packages/nuqs/src/lib/url-encoding.ts#L3

This would make it possible to modify the query parameters before they are persisted to the URL, allowing them, for instance, to be passed through qs to achieve the desired format. Additionally, you would need the same sort of option for parsing it back again.