Support localePrefix setting per domain #1105
Closed
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 ↗︎
|
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.
Related to #1055
This pull request introduces the ability to specify a
localePrefixsetting per domain in the Next.js internationalization middleware configuration.localePrefixproperty toDomainConfigtype: TheDomainConfigtype inpackages/next-intl/src/middleware/NextIntlMiddlewareConfig.tsxnow includes alocalePrefixproperty. This allows for domain-specific locale prefix settings, enabling more granular control over locale handling.localePrefixproperty is optional and does not affect existing configurations that do not use this property. This ensures that current implementations will continue to work without modification.For more details, open the Copilot Workspace session.