feat: avoid refresh if new locale is already the current locale #322
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
|
@moinulmoin is attempting to deploy a commit to the Tom Team on Vercel. A member of the Team first needs to authorize it. |
QuiiBz
requested changes
Jan 1, 2024
packages/next-international/src/app/client/create-use-change-locale.ts
Outdated
Show resolved
Hide resolved
Happy New Year! 🎉 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
QuiiBz
changed the title
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.
So, currently, if we set the locale that is already set, it rerenders the page. To avoid this, I think an early locale check would be helpful.
Here is the record:
https://github.com/QuiiBz/next-international/assets/63459189/fa926b15-97dc-4ecb-b41e-9aac8f21cca5