Relative Link '..' is pathname based and not route-based #5382
Unanswered
codeart1st
asked this question in
Q&A
Replies: 1 comment
-
Should be do the trick, but maybe this behavior should be the default for '..' relative paths. |
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 seems that using
<Link to='..'>
only removes the latest segment from pathname instead of going to the actual parent route. What's the best solution to get a link for the real upper route in every scenario? I have a generic route error component with a link to the next parent overview page.Routes:
/
/overview
/overview/some/more/fragments
<Link to='..'>
from/overview/some/more/fragments
to/overview/some/more
instead of/overview
.router/packages/router-core/src/path.ts
Lines 178 to 180 in 84fdb44
Beta Was this translation helpful? Give feedback.
All reactions