Fix split translations in workspace.distanceRates#73331
Fix split translations in workspace.distanceRates#73331youssef-lr merged 7 commits intoExpensify:mainfrom
Conversation
Codecov Report❌ Patch coverage is
... and 5 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
Good catch Jon - totally agree. That should be using our |
|
@dubielzyk-expensify can we make the parent issue for $250 so that we can fix this bug in the same PR? otherwise such issues are reported through normal bug process |
|
I'll let @eh2077 figure out that bit. We can also file it separately. I don't mind. |
|
Yeah, I think we can handle it separately |
Reviewer Checklist
Screenshots/VideosMacOS: Chrome / SafariScreen.Recording.2025-11-05.at.3.33.06.PM.mov |
| return onLinkPress ? ( | ||
| <RenderHTMLConfigProvider | ||
| defaultTextProps={{selectable: true}} | ||
| renderersProps={renderersProps} | ||
| > | ||
| {htmlSource} | ||
| </RenderHTMLConfigProvider> | ||
| ) : ( | ||
| htmlSource | ||
| ); |
There was a problem hiding this comment.
I'm not sure if it is a good pattern to conditionally wrap with config provider.
There was a problem hiding this comment.
@eh2077 we got this code merged in another PR, what do you suggest instead? i can update it in this PR
There was a problem hiding this comment.
Okay, then I think it should be fine.
| // Configuration for RenderHTML is handled in a top-level component providing | ||
| // context to RenderHTMLSource components. See https://git.io/JRcZb | ||
| // The provider is available at src/components/HTMLEngineProvider/ | ||
| function RenderHTML({html: htmlParam}: RenderHTMLProps) { | ||
| function RenderHTML({html: htmlParam, onLinkPress}: RenderHTMLProps) { |
There was a problem hiding this comment.
The render config is handled in HTMLEngineProvider as mentioned, this change will conflict with it. I think it's better to make it consistent.
There was a problem hiding this comment.
sorry didn't quite catch that can you reference the code for what you are trying to say?
There was a problem hiding this comment.
I think this comment can be marked as resolved too because the change isn't in this PR.
|
Hey, I noticed you changed If you want to automatically generate translations for other locales, an Expensify employee will have to:
Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running: npx ts-node ./scripts/generateTranslations.ts --helpTypically, you'd want to translate only what you changed by running |
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.2.46-0 🚀
|
|
🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.46-3 🚀
|








Explanation of Change
Fixed Issues
$ #72054
PROPOSAL: #72054 (comment)
Tests
Offline tests
QA Steps
Verify that the track tax toggle is disabled and the subtext is displayed correctly
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop