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
[9.5.6-canary.9][i18n] next/link does not handle cross-locale links correctly #18086
Comments
We changed the behavior a bit from the RFC as it turned out that linking around using just the path has issues. You can use |
Thanks for explaining @timneutkens. This solution doesn't sound good to me because I receive full slugs from a CMS including locale in the path already, like |
Will discuss with the team and see what we can do for this use case 🙏 |
Would you mind sharing a bit more info on the issues that came up? My solution just prepends the locale automatically, but there are no underlying changes made in Next in my case. Autoprepending has been very convenient though so I'd love to see this. |
We're currently discussing adding @ljosberinn say you have a locale set up like |
Yes, one case would be when you have a page that has the same name as a locale. |
Yes, that works for me. Thank you. Will the same behavior be performed using |
@rokinsky yeah |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Bug report
Describe the bug
I'm trying to use the experimental i18n feature (#17078) and it seems like
next/link
does not handle cross-locale links correctly.To Reproduce
Repository: next.js-bug-link-locale
Steps to reproduce the behavior:
Expected behavior
Visiting http://localhost:3000/de-de/42 without errors
Screenshots
System information
Additional context
N/A
The text was updated successfully, but these errors were encountered: