An option to skip values matching defaults from createSerializer(parsers)(values) output

[ivan-kleshnin]

Is there an option to skip values matching defaults from createSerializer(parsers)(values) output?

So, e.g. serializer(...) here:

const parsers = {
  contacts: parseAsArrayOf(parseAsString).withDefault([]),
}

const serializer = createSerializer(parsers)
serializer(url, values) // !!!

would return "?" or an empty string instead of "?contacts=". It's easier to visually debug URL issues when URLs are short and in my project we may have tens of filters most of which would be keys representing the default case.

Here's a similar issue but it ends up with accepting null value and avoiding defaults as a solution.

I don't see it as an acceptable solution, I would like to avoid null-containing unions to keep TS types clean.

I see no technical blocker that would make the goal of avoiding query params matching their defaults non-achievable.

[franky47]

It could be a matter of checking the value against the default (if any, and using the eq property of the parser to handle non-primitives like arrays), and skipping adding it to the output. This should probably be an option, as in some cases you might want explicit current defaults, since those can change over the lifetime of the app.

Would you like to open a PR?

[franky47]

FYI, this is being worked on in #720 and should land in v2.1.0.