-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
fix: Dynamic keys for useQueryStates #858
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
packages/nuqs/src/useQueryStates.test.ts:296
- The expectation for result.current[0].d should be consistent with other checks. It should be expect(result.current[0].d).toBeUndefined().
expect(result.current[0].d).toBeNull()
packages/nuqs/src/useQueryStates.ts:116
- Comparing the joined strings of keys and values is unconventional and error-prone. Consider comparing the lengths of the arrays instead.
Object.keys(queryRef.current).join('&') !== Object.values(resolvedUrlKeys).join('&')
c5f62b1
to
ff2570f
Compare
ff2570f
to
33511f5
Compare
33511f5
to
3576988
Compare
Anything I can do to help get this merged :) ? |
Awesomeness how do we get it to npm? |
🎉 This PR is included in version 2.3.2-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
It's available in beta, I have a few other things to test/merge and it will land in latest later this week. |
Tasks
Closes #799.