Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Allow chaining parser options & default values #387

Merged
merged 2 commits into from
Nov 8, 2023

Conversation

franky47
Copy link
Member

@franky47 franky47 commented Nov 3, 2023

Rather than adding another method, extend the types to allow chaining options and setting default values regardless of order.

Runtime was mostly fine except for a bug where re-setting a default value would not work for server-side parsing.

Closes #386.

Copy link

vercel bot commented Nov 3, 2023

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

Name Status Preview Comments Updated (UTC)
next-usequerystate ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 8, 2023 0:33am

@franky47 franky47 force-pushed the feat/386-parsers-config-chaining branch from 64621b8 to a33ae12 Compare November 8, 2023 12:32
@franky47 franky47 enabled auto-merge (rebase) November 8, 2023 12:34
@franky47 franky47 merged commit 207240a into next Nov 8, 2023
4 checks passed
@franky47 franky47 deleted the feat/386-parsers-config-chaining branch November 8, 2023 12:34
Copy link

github-actions bot commented Nov 8, 2023

🎉 This PR is included in version 1.10.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

github-actions bot commented Nov 8, 2023

🎉 This PR is included in version 1.10.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@franky47 franky47 mentioned this pull request Jan 16, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better configuration story
1 participant