Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: 15131 html decode in lhn and iou #16957

Merged
merged 3 commits into from
Apr 13, 2023

Conversation

tienifr
Copy link
Contributor

@tienifr tienifr commented Apr 5, 2023

Details

Fixed Issues

$ #16819
$ #15131
PROPOSAL: #15131 (comment)

Tests

  • LHN should show the last message
  1. Go to chat
  2. Enter &nbsp
  3. Verify LHN should show &nbsp
  4. Enter *abc*
  5. Verify LHN should show *abc*
  • IOU cancelling message shouldn't display escaped html characters
  1. Go to chat
  2. Request money with IOU message contains HTML characters, like Tokyo <> Mexico
  3. Click sent IOU message to open IOU details page
  4. Click cancel money request
  5. Verify IOU cancelling message should display Tokyo <> Mexico
  • iou message should not be flicker when user goes offline then online again
  1. Go to chat
  2. Go offline
  3. Request money
  4. Enter amount and click Next
  5. Type What's it for message: test abc &nbsp
  6. Click request button
  7. Verify the message in report should be test abc &nbsp
  8. Go online
  9. Verify the message in report should be test abc &nbsp and shouldn't be flicker
  • Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

  • LHN should show the last message
  1. Go to chat
  2. Enter &nbsp
  3. Verify LHN should show &nbsp
  4. Enter *abc*
  5. Verify LHN should show *abc*
  • IOU cancelling message shouldn't display escaped html characters
  1. Go to chat
  2. Request money with IOU message contains HTML characters, like Tokyo <> Mexico
  3. Click sent IOU message to open IOU details page
  4. Click cancel money request
  5. Verify IOU cancelling message should display Tokyo <> Mexico
  • iou message should not be flicker when user goes offline then online again
  1. Go to chat
  2. Go offline
  3. Request money
  4. Enter amount and click Next
  5. Type What's it for message: test abc &nbsp
  6. Click request button
  7. Verify the message in report should be test abc &nbsp
  8. Go online
  9. Verify the message in report should be test abc &nbsp and shouldn't be flicker
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (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 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
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 correct English and 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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Screen.Recording.2023-04-05.at.16.17.41.mov

iou message should not be flicker when user goes offline then online again:

Screen.Recording.2023-04-11.at.15.08.28.mp4
Mobile Web - Chrome

https://user-images.githubusercontent.com/113963320/230040355-67afaad4-be36-4b74-b855-caaae53d910c.mp4
iou message should not be flicker when user goes offline then online again:

RPReplay_Final1681200919.mp4
Mobile Web - Safari
RPReplay_Final1680686249.mp4

iou message should not be flicker when user goes offline then online again:

RPReplay_Final1681200766.mp4
Desktop

https://user-images.githubusercontent.com/113963320/230041357-a7ceb2a9-aa3c-4b43-9c20-6c06a71d98da.mp4
iou message should not be flicker when user goes offline then online again:

Screen.Recording.2023-04-11.at.15.25.40.mp4
iOS
Screen-Recording-2023-04-11-at-16.55.21.mp4

iou message should not be flicker when user goes offline then online again:

Screen-Recording-2023-04-11-at-16.57.51.mp4
Android
Untitled5.mp4
Untitled6.mp4

@tienifr tienifr marked this pull request as ready for review April 5, 2023 09:35
@tienifr tienifr requested a review from a team as a code owner April 5, 2023 09:35
@melvin-bot melvin-bot bot requested review from MariaHCD and rushatgabhane and removed request for a team April 5, 2023 09:35
@MelvinBot
Copy link

@MariaHCD @rushatgabhane One of you needs to 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]

Copy link
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

Changes look good. But let's make sure it works in all test conditions.

Screenshots/Videos

Web
Screen.Recording.2023-04-05.at.17.47.13.mov
Desktop Screenshot 2023-04-05 at 17 54 06 Screenshot 2023-04-05 at 17 53 35

@sobitneupane
Copy link
Contributor

sobitneupane commented Apr 6, 2023

@tienifr
Found a bug.

Being offline, If you request money first and the cancel money, html entities (like &nbsp, &#38) in comment will de decoded.

@rushatgabhane
Copy link
Member

@sobitneupane all yours to review :)

@tienifr
Copy link
Contributor Author

tienifr commented Apr 7, 2023

@sobitneupane After investigating I see the problem in

moneyRequestAction.originalMessage.comment,

If user is offline, the originalMessage will be &nbsp

Screen Shot 2023-04-07 at 17 45 34

but after go online, it's updated to &amp;nbsp
Screen Shot 2023-04-07 at 17 46 48

That makes the inconsistency between online and offline mode.

Solution: We can update function buildOptimisticIOUReportAction by changing the originalMessage:

   const parser = new ExpensiMark();
   const commentText = getParsedComment(comment);
   const textForNewComment = parser.htmlToText(commentText)
   const textFotNewCommentDecode = Str.htmlDecode(textForNewComment)
   const originalMessage = {
       amount,
       comment:textForNewComment,
       currency,
       IOUTransactionID,
       IOUReportID,
       type,
   };

...
       message: getIOUReportActionMessage(type, amount, participants, textFotNewCommentDecode, currency, paymentType, isSettlingUp),

But I don't think it's a good idea, we should preserve the comment as its name originalMessage.
Please tell me what your thought. Thanks

@sobitneupane
Copy link
Contributor

@tienifr I think we should change the frontend to match the backend if it won't cause any regression.

@tienifr
Copy link
Contributor Author

tienifr commented Apr 10, 2023

@sobitneupane I updated my PR to fix this issue: #16957 (comment)
Here is the result:

Screen.Recording.2023-04-10.at.15.03.45.mp4

@sobitneupane
Copy link
Contributor

sobitneupane commented Apr 10, 2023

Thanks for the update @tienifr. Can you please update the screenshots. Also, Offline Test Steps are missing in PR body

@tienifr
Copy link
Contributor Author

tienifr commented Apr 11, 2023

@sobitneupane I've added the screenshots, and PR body. Please help take a look. Thanks

Copy link
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

Screenshots/Videos

Web
Screen.Recording.2023-04-12.at.13.37.11.mov
Mobile Web - Chrome
Screen.Recording.2023-04-12.at.14.02.54.mov
Mobile Web - Safari
Screen.Recording.2023-04-12.at.13.51.15.mov
Desktop
Untitled.mov
iOS
Screen.Recording.2023-04-12.at.13.57.03.mov
Android
Screen.Recording.2023-04-12.at.13.59.24.mov

Copy link
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

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 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 correct English and 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 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.

@sobitneupane
Copy link
Contributor

Changes look good and test well

cc: @pecanoro

@MariaHCD MariaHCD removed the request for review from rushatgabhane April 12, 2023 12:37
@MariaHCD MariaHCD requested a review from pecanoro April 12, 2023 13:10
Copy link
Contributor

@pecanoro pecanoro left a comment

Choose a reason for hiding this comment

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

@tienifr So the PR works well, but I am wondering why we decided to do all this dance with htmlDecode and we are not repeating what we do with requestMoney for example?

function requestMoney(report, amount, currency, recipientEmail, participant, comment) {
const debtorEmail = OptionsListUtils.addSMSDomainIfPhoneNumber(participant.login);
let chatReport = lodashGet(report, 'reportID', null) ? report : null;
let isNewChat = false;
if (!chatReport) {
chatReport = ReportUtils.getChatByParticipants([debtorEmail]);
}
if (!chatReport) {
chatReport = ReportUtils.buildOptimisticChatReport([debtorEmail]);
isNewChat = true;
}
let iouReport;
if (chatReport.iouReportID) {
iouReport = IOUUtils.updateIOUOwnerAndTotal(
iouReports[`${ONYXKEYS.COLLECTION.REPORT}${chatReport.iouReportID}`],
recipientEmail,
amount,
currency,
);
} else {
iouReport = ReportUtils.buildOptimisticIOUReport(recipientEmail, debtorEmail, amount, chatReport.reportID, currency, preferredLocale);
}
// Note: The created action must be optimistically generated before the IOU action so there's no chance that the created action appears after the IOU action in the chat
const optimisticCreatedAction = ReportUtils.buildOptimisticCreatedReportAction(recipientEmail);
const optimisticReportAction = ReportUtils.buildOptimisticIOUReportAction(
CONST.IOU.REPORT_ACTION_TYPE.CREATE,
amount,
currency,
comment,
[participant],
'',
'',
iouReport.reportID,
);

@tienifr
Copy link
Contributor Author

tienifr commented Apr 13, 2023

@pecanoro With requestMoney we're passing the comment state instead of originalMessage:

IOU.requestMoney(
props.report,
Math.round(amount * 100),
props.iou.selectedCurrencyCode,
props.currentUserPersonalDetails.login,
selectedParticipants[0],
trimmedComment,
);

The originalMessage is encoded but not comment state. That why we don't need to decode the comment in this case

@pecanoro
Copy link
Contributor

@tienifr Gotcha, thank you for the explanation! Hopefully we solve everything with this and we can forget about it hehe

@pecanoro pecanoro merged commit 1f53560 into Expensify:main Apr 13, 2023
@OSBotify
Copy link
Contributor

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

@@ -247,7 +247,7 @@ function getOptionData(reportID) {
if (ReportUtils.isReportMessageAttachment({text: report.lastMessageText, html: report.lastMessageHtml})) {
lastMessageTextFromReport = `[${Localize.translateLocal('common.attachment')}]`;
} else {
lastMessageTextFromReport = Str.htmlDecode(report ? report.lastMessageText : '');
lastMessageTextFromReport = _.get(report, 'lastMessageText', '');
Copy link
Contributor

Choose a reason for hiding this comment

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

This line causes a crash on iOS, when we get lastMessageText: null then it is causing the crash

Simulator Screen Shot - iPhone 14 - 2023-04-14 at 09 44 56

cc: @tienifr @sobitneupane @pecanoro @MariaHCD

Copy link
Contributor

Choose a reason for hiding this comment

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

@tienifr Let's get this sorted asap.

Copy link
Member

@rushatgabhane rushatgabhane Apr 14, 2023

Choose a reason for hiding this comment

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

@sobitneupane if you are free now, please raise a PR as this makes app unusable

@tienifr might be in a different timezone so

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for catching this, @jayeshmangwani! Is anyone currently working on a fix? 👀

Copy link
Contributor

Choose a reason for hiding this comment

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

Created PR #17449

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@sobitneupane Thanks for your quick PR. I'm really sorry for this delay. Do you need any help?

Copy link
Contributor

Choose a reason for hiding this comment

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

@tienifr If you are available, can you please review the PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, sure

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/pecanoro in version: 1.3.1-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.1-3 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants