Replies: 2 comments 1 reply
-
did you find the best way to test the query params? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi, we have a similar usecase where we test custom SearchParams handling with the help from the HistoryRouter. therefore an export of the History type (which in v6 was compatible with the one from the history package) and createHistoryRouter would be extremely helpful. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be great if v7 continued to export the
createMemoryHistory
function, similar toUNSAFE_createBrowserHistory
. We currently require this in order to test our custom method for preserving search params, regardless of the interaction method used (i.e.<Link />
ornavigate
). I'm happy to replace our approach with acreateBrowserRouter
-native one but I can't seem to find an extension point that gives this same reliable behavior? AFAIK, any alternative would involve manually specifying the destination search string.Beta Was this translation helpful? Give feedback.
All reactions