We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given I'm on a page /show/home/fiction/333
/show/home/fiction/333
and I call const navigate = useNavigate(); navigate("../similar/333")
It redirects to /show/home/fiction/333/../similar/333
/show/home/fiction/333/../similar/333
None
Described above
Expecting Router to support relative paths It should redirect to /show/home/similar/333
/show/home/similar/333
No response
Mac + Chrome
The text was updated successfully, but these errors were encountered:
I assume it's not supported...
Doesn't look like this is doing any logic to check for ../ or ./
../
./
Sorry, something went wrong.
Yeah we never implemented relative paths like that.
Are you planning on supporting this or should I go with absolute paths?
No branches or pull requests
Describe the bug
Given I'm on a page
/show/home/fiction/333
and I call
const navigate = useNavigate();
navigate("../similar/333")
It redirects to
/show/home/fiction/333/../similar/333
Your Example Website or App
None
Steps to Reproduce the Bug or Issue
Described above
Expected behavior
Expecting Router to support relative paths
It should redirect to
/show/home/similar/333
Screenshots or Videos
No response
Platform
Mac + Chrome
Additional context
No response
The text was updated successfully, but these errors were encountered: