Skip to content

feat(wordpress): add wordpress namespace with Phase 2 admin + widget strings#55

Merged
haim-barad merged 1 commit into
mainfrom
feat/wordpress-phase2-strings
Apr 14, 2026
Merged

feat(wordpress): add wordpress namespace with Phase 2 admin + widget strings#55
haim-barad merged 1 commit into
mainfrom
feat/wordpress-phase2-strings

Conversation

@haim-barad

@haim-barad haim-barad commented Apr 14, 2026

Copy link
Copy Markdown
Member

User description

Summary

Adds the wordpress i18next namespace across all 8 locales for the LoyaltyDog WordPress plugin Phase 2.

New files: packages/i18n/locales/{en-US,en-GB,es-ES,es-MX,fr,it,pt-BR,pt-PT}/wordpress.json

Key groups:

  • wordpress.admin.dashboard — connection status, program info, open dashboard link
  • wordpress.admin.connection — API key display, test connection, health indicator
  • wordpress.admin.widget — shortcode reference, WC tab toggle, preview section
  • wordpress.admin.systemInfo — PHP/WP/WC versions, encryption status, AS queue
  • wordpress.widget — points balance, tier, recent transactions, join CTA

Note: These are bookkeeping keys. The WordPress plugin itself uses WordPress-standard .pot/.po/.mo gettext files (shipped in the plugin repo). These i18next keys are registered here for consistency with the rest of the platform's string inventory.

Test plan

  • npm test passes in packages/i18n
  • All 8 locale files parse as valid JSON
  • Key structure matches en-US/wordpress.json across all locales

🤖 Generated with Claude Code


CodeAnt-AI Description

Add WordPress admin and widget strings for all supported locales

What Changed

  • Added WordPress dashboard, connection, widget, and system info text for the plugin UI in 8 locales
  • Added user-facing messages for connection status, copy actions, preview text, and login/join prompts
  • Added locale-specific wording for US, UK, Spanish, French, Portuguese, and Italian variants

Impact

✅ WordPress admin screens can show translated text
✅ Clearer setup and connection messages for store owners
✅ Localized widget prompts for customers

🔄 Retrigger CodeAnt AI Review

Details

💡 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:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

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:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

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.

…strings

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@codeant-ai

codeant-ai Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:L This PR changes 100-499 lines, ignoring generated files label Apr 14, 2026
@haim-barad haim-barad self-assigned this Apr 14, 2026
@codeant-ai

codeant-ai Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

CodeAnt AI finished reviewing your PR.

@paperclip-access paperclip-access Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review: PR #55

Files changed: 2 new locale JSON files for WordPress Phase 2 admin + widget strings (en-GB, en-US)

Assessment: APPROVE

Pure i18n resource addition — no functional code. JSON structure is valid and follows existing locale conventions. British spelling (programme) is consistent with en-GB locale standards. No security concerns or logic issues.

Note: Other locales not updated here — ensure a translation fallthrough strategy exists for unsupported locales at runtime.

@haim-barad haim-barad merged commit e101bcb into main Apr 14, 2026
7 checks passed
@haim-barad haim-barad deleted the feat/wordpress-phase2-strings branch April 14, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant