Frontend/i18n: Remove inline <Trans> text#9211
Conversation
MobileInstall the Dev Tool (iOS via TestFlight, iOS Simulator, or Android .apk) here. Scan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client.
Deep linksiOS Android Web (Vercel)View the Vercel web preview for this branch. Backend
Other
|
nabramow
left a comment
There was a problem hiding this comment.
Oh great, I always thought this seemed a bit weird! I tested a couple and seems okay to me!
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR is primarily an internal i18n/code cleanup that removes duplicated inline translation text and aligns the frontend with existing translation strings. While it may fix a few stale wording mismatches, it does not introduce a new user-facing feature or a significant end-user-visible bug fix on its own. 🤖 Bot Debug InformationModel: |


Our
<Trans>tags often included a copy of the string fromen.json, which unavoidably lead to the two drifting apart as noted in #9008. It turns out we don't have to do that and can simply provide the components to be instantiated by the string without duplicating the text.Closes #9008
Testing
Used vercel preview to spot check:
ProfileIncompleteDialogStrongVerificationPage(note the text is from the more recenten.json, the inline text was stale)PushNotificationSettingWeb frontend checklist
For maintainers