-
Notifications
You must be signed in to change notification settings - Fork 98
Feature/unmutable set value #46
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
Conversation
unmutable setValue in useQueryParam
…ture/unmutable-set-value
…ture/unmutable-set-value
Sorry I'm not sure I entirely understand what's happening here. Can you add a test that fails with the current implementation to demonstrate the problem? |
I must indicate the setter as a dependency of the effect because otherwise I will get an lint error:
|
👍 please merge. |
Any update on getting this merged and released? |
Thanks for finding this and providing a fix! I ended up modifying some more memoization issues/react hook dependencies at the same time. Will publish in v0.4.2 |
Hello! I noticed that the location object is constantly changing. Because of this, the method for setting a new value also changes. Therefore, using the method to set a new value as deps leads to a repeated call of the effect.