feat: Add localePrefix
for navigation APIs for an improved initial render of Link
when using localePrefix: never
. Also fix edge case in middleware when using localized pathnames for redirects that remove a locale prefix (fixes an infinite loop).
#678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By accepting an optional
localePrefix
for the navigation APIs, we can get the initial render of thehref
ofLink
right iflocalePrefix: 'never'
is set. This can be helpful if domain-based routing is used and you have a single locale per domain.Note that this change is backward-compatible. It's now recommended to set the
localePrefix
for the navigation APIs to get improved behavior forLink
in caselocalePrefix: 'never'
is used, but otherwise your app will keep working with the previous behavior.Ref #444