-
Notifications
You must be signed in to change notification settings - Fork 20
Adds support for history replace in useQueryParams
#135
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
Adds support for history replace in useQueryParams
#135
Conversation
|
@rithviknishad This looks great, and you even added a test! However, the actions jobs are all failing due to deprecations in the job themselves. I will need to fix this before I can get this merged. This might take me a few days, as my plate is pretty full this week. I will get to this though, I promise. |
Thanks! Would really love to see this released! Thanks for maintaining such a clean and minimal routing solution for react! |
|
@kyeotic If the workflows have been updated, could we rerun this? |
|
@rithviknishad You didnt give me permission to push to your fork, so I can't try this myself, so can you push an empty commit? Github doesn't seem to be running jobs on the correct base for main. |
…tion-for-useQueryParams
@kyeotic I've merged the latest main on to this branch; Could you try now? Weird, I had given you permission to push to my fork:
|
|
This has been published under 4.2.0 |

Added support for history replace when using
setQueryStringofuseQueryParamsby settinghistoryReplaceoption.Associated Issues
useQueryParamsAdds New History Entries When Updating Search Parameters #134