Alexey Taktarov
Alexey Taktarov
Hi @pReya, I don't think it's possible at the moment. In the current design, the context where parameters are stored gets overwritten in the Route, so parameters don't inherit.
I see. Your point is fair enough. I'm finalising everything for the v3 release (it's been in the rc for over 2 m already, so really want to publish it...
@mattkrins I know... This feature isn't hard to implement, however this will require every Route in the app to subscribe to the context to get the outer parameters. It will...
Ok, actually I am wrong. Thoughts: 1. Parameters only change when the current location changes (probably, I can't think of an edge-case) 2. Every route is also subscribed to current...
Released in https://github.com/molefrog/wouter/releases/tag/v3.3.0
@junwen-k Hi! My guess it that `useSearchParams` from RR isn't compatible with wouter and it requires a separate implementation which is wouter-specific. I have an idea, as an experiment, use...
Also, take a look at https://github.com/molefrog/wouter/pull/391
Right, I was able to reproduce it locally. What bothers me is that React Router also doesn't re-render when the query string changes from the outside. Try running: `history.pushState(null, "",...
> Not sure if running `history.pushState(null, "", "/?tab=3")` not working for `react-router` was due to that. I did some digging: React Router uses its own format of `state` object to...
Hey @junwen-k any update on this? I'm curious if you found out the issue.