[Wave 8 - ECard Transactions] Show %Name Spent:% on ReportPreview by grgia · Pull Request #29287 · Expensify/App

grgia · 2023-10-11T12:05:58Z

Details

Fixed Issues

Tests

Verify that no errors appear in the JS console
Create a few IOU transactions to a User
Get the transactionID of one of the transactions
merge false reimbursable flag onto that transaction

Onyx.merge('transactions_<YOUR TRANSACTION ID>', {reimbursable: false});

verify ReportPreview title is in format <Name> spent:

Offline tests

QA Steps

NO QA - we have not started sending non-reimbursable transactions to FE

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 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
  - 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 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 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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
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

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

…sactions.

cloudflare-workers-and-pages · 2023-10-11T12:06:25Z

Deploying with Cloudflare Pages

Latest commit:	`8786ad4`
Status:	✅ Deploy successful!
Preview URL:	https://f6db2fca.helpdot.pages.dev
Branch Preview URL:	https://georgia-cardtransactions-rep.helpdot.pages.dev

View logs

melvin-bot · 2023-10-11T12:16:12Z

@mananjadhav 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]

mananjadhav · 2023-10-12T18:52:56Z

@grgia Is this like ready for review? The reason I ask because I don't see any screenshots added.

grgia · 2023-10-12T21:47:20Z

@mananjadhav apologies, just saw your comment. Yes, this is ready for review. This is a high priority project with deadline and I will continue to add screenshots. Please do not hold checklist on that

melvin-bot · 2023-10-13T14:06:54Z

@thienlnam 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]

mananjadhav · 2023-10-13T14:07:35Z

Will finish this checklist in a while.

mananjadhav · 2023-10-13T17:06:48Z

@grgia Are we considering the header and copy to clipboard behavior in this?

header-and-copy-to-clipboard.mov

grgia · 2023-10-13T18:08:51Z

@mananjadhav

Are we considering the header and copy to clipboard behavior in this?

I'm not sure I follow, can you reword this?

grgia · 2023-10-13T18:29:36Z

Ah I see what you mean, yes I will update there too.

mananjadhav · 2023-10-13T18:29:54Z

@grgia When I perform the Onxy.merge operation, the preview shows <name> spent but if I copy the message to clipboard it says <name> owes.

The same for the header as well.

mananjadhav · 2023-10-13T18:41:20Z

The label changes just fine on Web and Desktop but when I try the same on mobile web it doesn't for Distance Requests. Can you please check once at your end? I checked the value is updated in Onyx. 1:1 request is updated.

spent-labels-mobile-web.mov

mananjadhav · 2023-10-13T18:41:56Z

@grgia Can you please fix the lint issues?

grgia · 2023-10-13T18:45:01Z

Screen.Recording.2023-10-13.at.7.43.41.PM.mov

grgia · 2023-10-13T18:53:36Z

For IOS and native, I also test by hard coding values

grgia · 2023-10-13T19:27:43Z

@mananjadhav for the distance requests transactions thing you brought up, could it be related to this:

App/src/libs/TransactionUtils.ts

Lines 383 to 385 in 47a6bcc

    
           // `reportID` from the `/CreateDistanceRequest` endpoint return's number instead of string for created `transaction`. 
        
           // For reference, https://github.com/Expensify/App/pull/26536#issuecomment-1703573277. 
        
           // We will update this in a follow-up Issue. According to this comment: https://github.com/Expensify/App/pull/26536#issuecomment-1703591019.

mananjadhav · 2023-10-13T19:37:59Z

Yeah I think it worked though. I am just working on the checklist.

mananjadhav · 2023-10-13T19:41:17Z

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
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-lhs-header-copy-text-spent-label.mov

Mobile Web - Chrome

mweb-chrome-spent-label.mov

Mobile Web - Safari

Desktop

iOS

Android

mananjadhav · 2023-10-13T19:42:04Z

@grgia Just finished testing and adding the screenshots.

@thienlnam All yours.

melvin-bot · 2023-10-13T20:19:34Z

@thienlnam looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

thienlnam · 2023-10-13T20:20:01Z

Tests were passing :hmm:

OSBotify · 2023-10-13T20:26:22Z

✋ 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-10-13T21:09:52Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.84-0 🚀

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

OSBotify · 2023-10-16T21:10:17Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-16T21:46:37Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

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

OSBotify · 2023-10-16T21:49:33Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.85-0 🚀

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

OSBotify · 2023-10-17T23:14:18Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.85-4 🚀

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

grgia added 2 commits October 11, 2023 13:02

Show <Name Spent:> on ReportPreview if there are nonreimbursable tran…

23db315

…sactions.

Remove unused function

99494f4

grgia self-assigned this Oct 11, 2023

prettier

167ea63

grgia marked this pull request as ready for review October 11, 2023 12:16

grgia requested a review from a team as a code owner October 11, 2023 12:16

melvin-bot bot requested review from mananjadhav and removed request for a team October 11, 2023 12:16

grgia changed the title ~~[Wave 8] Show %Name Spent:% on ReportPreview~~ [Wave 8 - ECard Transactions] Show %Name Spent:% on ReportPreview Oct 11, 2023

mananjadhav approved these changes Oct 13, 2023

View reviewed changes

melvin-bot bot requested a review from thienlnam October 13, 2023 14:06

Merge branch 'main' into georgia-cardTransactions-ReportPreview

47a6bcc

Update helper functions

f748a17

fix error with same function/var name

8786ad4

thienlnam approved these changes Oct 13, 2023

View reviewed changes

thienlnam merged commit 5218714 into main Oct 13, 2023

thienlnam deleted the georgia-cardTransactions-ReportPreview branch October 13, 2023 20:19

melvin-bot bot added the Emergency label Oct 13, 2023

thienlnam removed the Emergency label Oct 13, 2023

OSBotify mentioned this pull request Oct 13, 2023

Deploy Checklist: New Expensify 2023-10-13 #29585

Closed

97 tasks

OSBotify mentioned this pull request Oct 16, 2023

Deploy Checklist: New Expensify 2023-10-16 #29717

Closed

melvin-bot bot mentioned this pull request Oct 16, 2023

[HOLD for payment 2023-10-23] [ECard Transactions] Update ReportPreview Title #28833

Closed

Charan-hs mentioned this pull request Oct 17, 2023

[$500] Inconsistent Usage of 'Paid' and 'Spent' in Request Money Details #29796

Closed

6 tasks

Conversation

grgia commented Oct 11, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

cloudflare-workers-and-pages bot commented Oct 11, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Pages

Uh oh!

melvin-bot bot commented Oct 11, 2023

Uh oh!

mananjadhav commented Oct 12, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

grgia commented Oct 12, 2023

Uh oh!

melvin-bot bot commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

grgia commented Oct 13, 2023

Uh oh!

grgia commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

grgia commented Oct 13, 2023

Uh oh!

grgia commented Oct 13, 2023

Uh oh!

grgia commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

mananjadhav commented Oct 13, 2023

Reviewer Checklist

Screenshots/Videos

Uh oh!

mananjadhav commented Oct 13, 2023

Uh oh!

melvin-bot bot commented Oct 13, 2023

Uh oh!

thienlnam commented Oct 13, 2023

Uh oh!

OSBotify commented Oct 13, 2023

Uh oh!

OSBotify commented Oct 13, 2023

Uh oh!

OSBotify commented Oct 16, 2023

Uh oh!

OSBotify commented Oct 16, 2023

Uh oh!

OSBotify commented Oct 16, 2023

Uh oh!

OSBotify commented Oct 17, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

grgia commented Oct 11, 2023 •

edited

Loading

cloudflare-workers-and-pages bot commented Oct 11, 2023 •

edited

Loading

mananjadhav commented Oct 12, 2023 •

edited

Loading