-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix i18n current locale #12839
base: main
Are you sure you want to change the base?
Fix i18n current locale #12839
Conversation
🦋 Changeset detectedLatest commit: 048dd65 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
CodSpeed Performance ReportMerging #12839 will not alter performanceComparing Summary
|
(routeData.pattern.test(url.pathname) | ||
? routeData | ||
: routeData.fallbackRoutes.find((fallbackRoute) => | ||
fallbackRoute.pattern.test(url.pathname), | ||
)) ?? routeData; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the past we used these operators and they made the readability worse, and we decided to use simple if/else. We would appreciate it if we keep using them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing. Will rewrite the logic here.
Changes
Testing
Adds similar logic to
computeCurrentLocale
as was used in #12709 to handle SSR manifests with fallback routes.Welcome feedback from a maintainer on whether there may be a more elegant solution to solve both of these - I dont have enough background on the decision process behind having such different manifests and i18n implementation between dev/SSR/SSG.
Docs
Just corrects a bug and inconsistent behavior across modes. No new docs needed.