You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Router>
// all sorts of normal app stuff
// ...
// ... deep in a nested component
<Popup><MemoryRouterinitialEntries={[match.url]}><ComponentWithRoutesThatIsAlsoUsedWithNormalRouer/></MemoryRouter></Popup></Router>
Expected Behavior
We needed a way to take a component that exists in our normal routes with history.back() and redirects and gingerly place it into a dialog popup WITHOUT having any of the routing paths show up in the browsers url and without our in-app back buttons sending the user away from the dialog and still getting to navigate deeper into the component. Wrapping the MemoryRouter around the component nested inside the main Router worked without a hitch. Gave us a little Router sandbox.
Actual Behavior
Now, in v6, we're barred from doing that. :(
Can this be a warning instead of an error?
Is there something else we could/should be doing?
The text was updated successfully, but these errors were encountered:
What version of React Router are you using?
6
Steps to Reproduce
Expected Behavior
We needed a way to take a component that exists in our normal routes with history.back() and redirects and gingerly place it into a dialog popup WITHOUT having any of the routing paths show up in the browsers url and without our in-app back buttons sending the user away from the dialog and still getting to navigate deeper into the component. Wrapping the MemoryRouter around the component nested inside the main Router worked without a hitch. Gave us a little Router sandbox.
Actual Behavior
Now, in v6, we're barred from doing that. :(
Can this be a warning instead of an error?
Is there something else we could/should be doing?
The text was updated successfully, but these errors were encountered: