Tim Dorr
Tim Dorr
`useNavigate` changes when the current location changes. It depends on it for relative navigation. Wrapping it in `memo` only prevents re-renders from parent components. If hooks within the component cause...
I'll be honest: I don't think this is going to be merged in. At a high level, you're creating scopes for Context values, which is not really how Context is...
Again, I think this is overcomplicating the issue. The problems with nested hooks like `useNavigate` or `useHref` can be resolved by setting `basename` on your nested `MemoryRouter`s. One thing we...
Correct, this has been fixed.
Can you please revert the changes to the compact imports? They are intentional. This is explained here: https://github.com/remix-run/react-router/blob/f3d87dcc91fbd6fd646064b88b4be52c15114603/packages/react-router-dom-v5-compat/index.ts#L1-L48
> With isomorphic component rendering, you may need to know the pathname and the pattern to render the correct component. I'm not sure I understand this statement. This is handled...
It's under this section: https://reactrouter.com/docs/en/v6/upgrading/v5#use-usenavigate-instead-of-usehistory
You should be using the new useOutletContext(), not trying to access the route context directly.
No, that is new as of [6.1.0](https://github.com/remix-run/react-router/releases/tag/v6.1.0). Please upgrade to a newer version, as you'll also get some bug fixes included.
I'm not sure if this makes sense. If you want to use your Users routes in multiple places, you wouldn't be able to. Not to mention Links/NavLinks would be harder...