fix: Serialization of default values in createSerializer

[hugotiger]

When using parsers in createSerializer it would not respect the clearOnDefault option properly when serializing, thus adding key-value pairs to the string that shouldn't be there.

An example:

const serialize = createSerializer({
    int: parseAsInteger.withOptions({ clearOnDefault: true }).withDefault(0)
})
const result = serialize({ int: 0 })
//    ^ Result is `?int=0` instead of empty string

Closes #641.

[vercel]

@hugotiger is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nuqs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2024 3:05pm

[franky47]

Thanks! Could you change back the base branch to next for this one? It's not a breaking change, so it can be published on the v1 release line.

I pushed a fix for the types to let parsers know they can have a default value.

[hugotiger]

Thanks! Could you change back the base branch to next for this one? It's not a breaking change, so it can be published on the v1 release line.

I pushed a fix for the types to let parsers know they can have a default value.

Awesome! Thanks for the help ✌️ Rebased now and updated the description of the PR.

[franky47]

One test is failing, see https://github.com/47ng/nuqs/actions/runs/10936702232/job/30378534527#step:7:90

[hugotiger]

One test is failing, see https://github.com/47ng/nuqs/actions/runs/10936702232/job/30378534527#step:7:90

I'm not able to reproduce it locally 🤔 Could it be some caching issue in the action? For context when I run pnpm run test it's all green.

[hugotiger]

One test is failing, see https://github.com/47ng/nuqs/actions/runs/10936702232/job/30378534527#step:7:90

I'm not able to reproduce it locally 🤔 Could it be some caching issue in the action? For context when I run pnpm run test it's all green.

I checked again now and it seems as if the CI was running on some previous commit. Could you do a rerun?

[franky47]

Thanks!

[github-actions]

🎉 This PR is included in version 1.19.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀