feat(i18n): add integrations.coming_soon badge label (8 locales)#58
Merged
Conversation
Companion to core_api PR #598 (Greptile P1 fix). The IntegrationTile
component shows a "Coming soon" badge on tiles whose status is
'coming_soon'. Previously the badge text was hardcoded English; PR #598
moved it behind useTranslation('marketing') against the new
`integrations.coming_soon` key.
This PR adds the canonical strings for that key in all 8 locales:
- en-US/en-GB: "Coming soon"
- es-ES/es-MX: "Próximamente" (matches the existing clover/square
descriptions in these locales)
- fr: "Bientôt disponible"
- it: "In arrivo"
- pt-BR/pt-PT: "Em breve"
en-US is hand-authored; the other 7 are Haiku-translated and
cross-checked against each locale's existing clover/square `desc`
phrasing for tone consistency.
Until merge, non-en-US users would see "Coming soon" via the en-US
fallback chain in i18next — still acceptable but not ideal. Once this
ships and Crowdin syncs (`crowdin upload sources`), the badge renders
in the merchant's selected language.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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 · |
codeant-ai
Bot
added
the
size:XS
Contributor
|
CodeAnt AI finished reviewing your PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
Summary
Adds
integrations.coming_soonto all 8 marketing locales for the dash root landing's "Coming soon" badge.en-US hand-authored; other 7 locales Haiku-translated and cross-checked against each locale's existing `clover`/`square` description phrasing for tone consistency.
Companion
core_api PR #598 — Greptile P1 fix that moved the "Coming soon" badge in `IntegrationTile.tsx` from a hardcoded English string to `t(M.integrations.comingSoon)`. The frontend already bundles the en-US value in `enUSFallback.marketing.integrations.coming_soon`; non-en-US locales fetch the translated value from the HTTP backend at runtime once this lands.
Test plan
clover.desc/square.desc🤖 Generated with Claude Code
CodeAnt-AI Description
Add localized “Coming soon” text for integration tiles
What Changed
Impact
✅ Localized integration badges✅ Clearer marketing pages for non-English users✅ Fewer English-only labels in the dashboard🔄 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:
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.