Type-safe multi-language support #367
Closed
Conversation
This file contains hidden or 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
|
@adambarath is attempting to deploy a commit to the medusajs Team on Vercel. A member of the Team first needs to authorize it. |
rostasigergo
approved these changes
Sep 18, 2024
adambarath
force-pushed
the
i18n
branch
2 times, most recently
from
9effe03 to
46d51b4
Compare
|
Hello and sorry for the very late reply. Someone else took a chance at this, so will be closing this PR for now |
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.
In this PR:
Example implementation to make a Store deployment easier to localise and have multi-language support by type-safe internationalization (i18n) for Next.js.
User now gets redirected to a localized page when they visit an url by handling countrycode param in middleware.
Related Issues/Questions:
#268
#109