Peter Beshai

You're essentially doing `withDefault(withDefault(DelimitedNumericArrayParam, [defaultValue]), newDefaultValue)` `withDefault()` internally first decodes with the param type and if undefined, provides the default value. In this case, it will always return `[defaultValue]` then...

You could modify withDefault to look at a `defaultValue` on the param object instead and then mutate that value, e.g. something like (untested): ```tsx function withStatefulDefault( param: QueryParamConfig, defaultValue: DefaultType,...

If you want to submit a PR that just removes that message, that's fine with me.

I think it's a reasonable option to have, but I don't want to add it at the moment. There are a few other options I'd like to support in the...

Personally I never want null in query params and only added in support for them for other folks who requested it. I can think of an example usage where maybe...

That being said, I believe currently you can pass in stringifyOptions to include skipNull: true. See https://github.com/sindresorhus/query-string#skipnull It wouldn't fix the types, not sure if I'd ever manage that 😓...

These cases are not currently possible with the current implementation: ```js [''] // would be ?foo= [null] // would be ?foo ``` Alternatives would be to disallow: ```js [] //...

Hi there, you're absolutely right about what's happening and it being undesirable. The way this hook works is that it uses React context that gets updated whenever the history changes...

Hmm, I suppose this is due to `window.location` not being a thing. I've never used next.js though, would you be able to reproduce this in an example repo I could...

If the adapter is working well, you're certainly welcome to PR it into this repo if you'd like. Thanks for taking the initiative on this work! 🙇