Why does `useLocation` re-render before navigation?
Assuming a simple route like this:
My naive assumption would be that the only value
Alternatively, we can also use the following:
But in that case,
One way to access the
Coming from react-router-dom, I have a couple questions:
- why do these APIs behave differently? I'm expecting the answer is along the lines of "X behaves like this because it's the internal state of the router, but Y behaves like this because..."
- what is the purpose of those different behaviors? something like "you should use X in situation A, but Y when you need B"
(Here's a demo of these behaviors for anyone interested: https://stackblitz.com/edit/tanstack-router-fpv611d5?file=src%2Froutes%2F_yo%2Fabout.tsx)
My naive assumption would be that the only value
pathname"/about"pathnameAlternatively, we can also use the following:
But in that case,
pathnameOne way to access the
pathnameComing from react-router-dom, I have a couple questions:
- why do these APIs behave differently? I'm expecting the answer is along the lines of "X behaves like this because it's the internal state of the router, but Y behaves like this because..."
- what is the purpose of those different behaviors? something like "you should use X in situation A, but Y when you need B"
(Here's a demo of these behaviors for anyone interested: https://stackblitz.com/edit/tanstack-router-fpv611d5?file=src%2Froutes%2F_yo%2Fabout.tsx)
