fix: primary locale url normalization#1219
Conversation
primaryLocales were not getting normalized, which led to a mismatch where "en-GB" in the locale and "en_gb" in the primaryLocale would be seen as different and the locale would be pre-prended.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
WalkthroughThis PR extends locale field normalization to include Sequence DiagramSee the diagrams embedded in the review stack layers above. Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
auto-screenshot-update: true
auto-screenshot-update: true
primaryLocales were not getting normalized, which led to a mismatch where "en-GB" in the locale and "en_gb" in the primaryLocale would be seen as different and the locale would be pre-prended.