feat(i18n): relabel platform.wordpress to "WordPress" (SWE-649)#63
Conversation
…SWE-649) The dashboard platform dropdown should display "WordPress" going forward (expanding beyond WooCommerce). Update the brand label across all 8 locales; like EposNow/Shopify it stays identical per locale. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
Greptile SummaryRenames the
Confidence Score: 5/5Safe to merge — a uniform one-line string rename in 8 locale files with no logic or schema impact. The change touches only the display label for the WordPress platform entry in the programs-edit dropdown. All 8 locale files are updated consistently, the key name is unchanged, and no other keys are affected. Existing WooCommerce-specific strings in wordpress.json and marketing.json are correctly left untouched. No files require special attention.
|
| Filename | Overview |
|---|---|
| packages/i18n/locales/en-US/common.json | Renames programs.edit.platform.wordpress from "WooCommerce" to "WordPress" — correct and consistent with the other locales. |
| packages/i18n/locales/en-GB/common.json | Same single-key rename as en-US; no issues. |
| packages/i18n/locales/es-ES/common.json | Spanish (Spain) platform label updated from "WooCommerce" to "WordPress"; correct brand name, no translation needed. |
| packages/i18n/locales/es-MX/common.json | Spanish (Mexico) platform label updated identically; no issues. |
| packages/i18n/locales/fr/common.json | French platform label updated to "WordPress"; correct. |
| packages/i18n/locales/it/common.json | Italian platform label updated to "WordPress"; correct. |
| packages/i18n/locales/pt-BR/common.json | Portuguese (Brazil) platform label updated to "WordPress"; correct. |
| packages/i18n/locales/pt-PT/common.json | Portuguese (Portugal) platform label updated to "WordPress"; correct. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[programs.edit.platform.wordpress key] --> B[Before PR: WooCommerce across all 8 locales]
A --> C[After PR: WordPress across all 8 locales]
C --> F[en-GB and en-US]
C --> G[es-ES and es-MX]
C --> H[fr and it]
C --> I[pt-BR and pt-PT]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[programs.edit.platform.wordpress key] --> B[Before PR: WooCommerce across all 8 locales]
A --> C[After PR: WordPress across all 8 locales]
C --> F[en-GB and en-US]
C --> G[es-ES and es-MX]
C --> H[fr and it]
C --> I[pt-BR and pt-PT]
Reviews (1): Last reviewed commit: "feat(i18n): relabel programs.edit.platfo..." | Re-trigger Greptile
User description
SWE-649 follow-up
The dashboard platform dropdown should display "WordPress" going forward (expanding support beyond WooCommerce). This updates
programs.edit.platform.wordpressfrom"WooCommerce"→"WordPress"across all 8 locales (brand name, identical per locale — same convention as EposNow/Shopify).Pairs with core_api PR #868, which relabels the 5 rule-form dropdowns and the edit-form i18n fallback to "WordPress" (and fixes the underlying validation bug).
Verification
🤖 Generated with Claude Code
CodeAnt-AI Description
Show WordPress in the platform dropdown instead of WooCommerce
What Changed
Impact
✅ Clearer platform naming✅ Less confusion for WordPress users✅ Consistent labels across locales💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.