chore(i18n): sync pt-BR key order and formatting#2104
chore(i18n): sync pt-BR key order and formatting#2104graphieros merged 2 commits intonpmx-dev:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis pull request updates the Portuguese (Brazil) locale JSON by adding new top-level i18n sections (blog, pds, privacy_policy, a11y) and expanding the profile section, plus numerous nested keys across UI areas (footer, shortcuts, search, settings, errors, view_on, action-bar and others). It introduces many new translations for blog workflow, privacy and cookie taxonomy, accessibility content, package/version UI labels, error/permission messages and instant_search keys, while reordering and refining several existing keys. Lines changed: roughly +342 / -332. Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 Tip CodeRabbit can use oxc to improve the quality of JavaScript and TypeScript code reviews.Add a configuration file to your project to customize how CodeRabbit runs oxc. |
|
@marlonwq I merged your previous PR first, you might want to take a look at the resulting conflicts |
When I went to fix it, I saw there were new keys.. You guys never stop, do you? haha I initially avoided adding new keys to keep the review simple, but since they just popped up, I figured I'd finish the job now |
🧭 Context
he
pt-BRlocale file was out of sync with the baseen.jsonstructure and key ordering📚 Description
his PR normalizes the
pt-BR.jsonfile using the project's official automation tool (pnpm i18n:check:fix). This ensures the file follows the expected alphabetical/structural order, reducing future diff noise for other contributors. It also includes the missing version keys translated in my previous PR #2103.