fix: Use redirect function from next-intl instead from next/navigation #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
soniaklimas
approved these changes
Dec 19, 2024
7 tasks
7 tasks
karolkarolka
added a commit
that referenced
this pull request
Jan 28, 2025
soniaklimas
pushed a commit
that referenced
this pull request
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Because of disabling locale detection in next-intl routing config here, we need to switch from using
redirectfunction fromnext-intlinstead of the defaultnext/navigationto not to redirect to the wrong locale.Also, I'm adding back the types for
next-intlredirectfunction export as it is still required for TypeScript.