-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<Link to> with relative link broken? #3085
Comments
Relative |
Now watching (but it does look like that issue died about a month ago rather than being on track). Can we at least reopen this issue and make its closing contingent on the API docs being appended with a note that Given that URLs are the backbone of the web, it's pretty important to let people know that |
It's not dead. We were waiting on some API changes with 2.0 so that we can work on it. |
Check #2933 if you have some documentation improvements. PRs are the best way to get it solved! 😄 |
They most certainly are! But I clearly don't know as much about I don't even know what code to write to get an current absolute path so I can even work around this issue. Is there some documentation or an issue that already explains that? (that was part two of my issue, really. How do I use Link if I can't do relative links? The docs don't seem to explain this anywhere and I don't see any stackoverflow questions on it either, especially with 2.0.0 being so recent) |
I have a router set up as
and in the
section1.jsx
have a<Link to='./details/'>details</Link>
, but this doesn't resolve correctly at all. The browser shows a link that "should" go to.../section/details
according to the browser status bar, but clicking it results in a react-router error instead:If I turn this
<Link>
into an<a>
things work find but of course then I lose all the benefits of navigation inspection etc.https://github.com/reactjs/react-router/blob/latest/docs/API.md#link does not say anything about relative links being broken, so: is this a bug, or is this intended? And if intended, what's the proper way to get a
<Link>
going to a relative path?The text was updated successfully, but these errors were encountered: