Fix: Wrong translation of `paid` in LHN after deleting last message #23778

tienifr · 2023-07-28T06:33:07Z

Details

The paid message in LHN is not translated correctly after deleting the last message. This PR fixes that.

Fixed Issues

$ #23380
PROPOSAL: #23380 (comment)

Tests

Login with account A and B on different devices
On A, change language to Spanish
On B, request money to A
On A, click green button to pay
Verify that in LHN, paid text is in Spanish (i.e. pagó {amount} de otra forma)
Send a message to B
Delete that message
Verify that in LHN, paid text is in Spanish (i.e. pagó {amount} de otra forma)

Verify that no errors appear in the JS console

Offline tests

NA

QA Steps

Login with account A and B on different devices
On A, change language to Spanish
On B, request money to A
Click green button to pay
On A, verify that in LHN, paid text is in Spanish (i.e. pagó {amount} de otra forma)
Send a message to B
Delete that message
Verify that in LHN, paid text is in Spanish (i.e. pagó {amount} de otra forma)

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Web

Screen.Recording.2023-07-28.at.13.46.41.mov

Mobile Web - Chrome

video_2023-07-28_13-52-42.mp4

Mobile Web - Safari

translation-safari-compressed.mov

Desktop

Screen.Recording.2023-07-28.at.13.53.06.mov

iOS

translation-compressed.mov

Android

translation-compressed.mov

melvin-bot · 2023-07-28T07:10:09Z

@ArekChr Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

ArekChr · 2023-07-28T12:21:50Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

web.mov

Mobile Web - Chrome

Mobile Web - Safari

Desktop

desktop.mov

iOS

ios.mov

Android

Nagranie.z.ekranu.2023-07-28.o.15.14.51.mov

ArekChr

LGTM !

ArekChr · 2023-07-28T13:21:41Z

There are still some paid translation issues, but this is inside the chat report view. I think that will be another issue.

OSBotify · 2023-07-28T16:37:11Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2023-07-31T18:58:13Z

🚀 Deployed to staging by https://github.com/johnmlee101 in version: 1.3.48-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-08-01T23:59:30Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.48-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-08-02T01:24:00Z

🚀 Deployed to staging by https://github.com/johnmlee101 in version: 1.3.49-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-08-03T18:16:27Z

🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.49-3 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

jjcoffee · 2023-11-23T07:39:33Z

src/libs/OptionsListUtils.js

-    const lastReportAction = lastReportActions[report.reportID];
+    const lastReportAction = _.find(
+        allSortedReportActions[report.reportID],
+        (reportAction, key) => ReportActionUtils.shouldReportActionBeVisible(reportAction, key) && reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE,


Just noting that the use of shouldReportActionBeVisible here caused a regression that caused the LHN subtitle to be incorrect (This is the beginning...), as shouldReportActionBeVisible is really for showing report actions in ReportActionList, so shouldReportActionBeVisibleAsLastAction is more appropriate here. More details here.

fix: wrong translation of paid message after deleting last message

4d605da

tienifr marked this pull request as ready for review July 28, 2023 07:10

tienifr requested a review from a team as a code owner July 28, 2023 07:10

melvin-bot bot requested review from ArekChr and removed request for a team July 28, 2023 07:10

tienifr mentioned this pull request Jul 28, 2023

[HOLD for payment 2023-08-08] [$1000] App translates paid message to english after deleting last message #23380

Closed

6 tasks

use const

1c31ef5

ArekChr approved these changes Jul 28, 2023

View reviewed changes

melvin-bot bot requested a review from johnmlee101 July 28, 2023 13:20

johnmlee101 approved these changes Jul 28, 2023

View reviewed changes

johnmlee101 merged commit fed84b5 into Expensify:main Jul 28, 2023
11 checks passed

OSBotify mentioned this pull request Jul 31, 2023

Deploy Checklist: New Expensify 2023-07-31 #23945

Closed

48 tasks

OSBotify mentioned this pull request Aug 1, 2023

Deploy Checklist: New Expensify 2023-08-01 #24028

Closed

79 tasks

jjcoffee mentioned this pull request Nov 2, 2023

[HOLD for payment 2023-11-22] [$500] Incorrect LHN subtitle when last message is flagged as assault #30575

Closed

6 tasks

jjcoffee reviewed Nov 23, 2023

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: Wrong translation of `paid` in LHN after deleting last message #23778

Fix: Wrong translation of `paid` in LHN after deleting last message #23778

tienifr commented Jul 28, 2023 •

edited

Loading

melvin-bot bot commented Jul 28, 2023

ArekChr commented Jul 28, 2023 •

edited

Loading

ArekChr left a comment

ArekChr commented Jul 28, 2023 •

edited

Loading

OSBotify commented Jul 28, 2023

OSBotify commented Jul 31, 2023

OSBotify commented Aug 1, 2023

OSBotify commented Aug 2, 2023

OSBotify commented Aug 3, 2023

jjcoffee Nov 23, 2023

Fix: Wrong translation of paid in LHN after deleting last message #23778

Fix: Wrong translation of paid in LHN after deleting last message #23778

Conversation

tienifr commented Jul 28, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jul 28, 2023

ArekChr commented Jul 28, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

ArekChr left a comment

Choose a reason for hiding this comment

ArekChr commented Jul 28, 2023 • edited Loading

OSBotify commented Jul 28, 2023

OSBotify commented Jul 31, 2023

OSBotify commented Aug 1, 2023

OSBotify commented Aug 2, 2023

OSBotify commented Aug 3, 2023

jjcoffee Nov 23, 2023

Choose a reason for hiding this comment

Fix: Wrong translation of `paid` in LHN after deleting last message #23778

Fix: Wrong translation of `paid` in LHN after deleting last message #23778

tienifr commented Jul 28, 2023 •

edited

Loading

ArekChr commented Jul 28, 2023 •

edited

Loading

ArekChr commented Jul 28, 2023 •

edited

Loading