Fix one-expense report loading by VickyStash · Pull Request #50147 · Expensify/App

VickyStash · 2024-10-03T13:31:32Z

Details

Fix one-expense report loading.

Fixed Issues

$ #49853
PROPOSAL: #49853 (comment)

Tests

Verify that no errors appear in the JS console

From User A create a one expense report as a submitter to User B.
From User A submit report for the approver to approve
Login the app as User B.
Open the report and make sure it loads as expected.

Offline tests

Same as in the Tests section.

QA Steps

Verify that no errors appear in the JS console

Same as in the Tests section.

PR Author Checklist

Screenshots/Videos

Android: Native

android.mp4

Android: mWeb Chrome

android_web.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

ios_web.mp4

MacOS: Chrome / Safari

web.mp4

MacOS: Desktop

desktop.mp4

melvin-bot · 2024-10-07T13:17:21Z

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

allroundexperts · 2024-10-07T13:18:04Z

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
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

Android: Native

Screen.Recording.2024-10-08.at.12.01.00.AM.mov

Android: mWeb Chrome

Screen.Recording.2024-10-07.at.11.59.51.PM.mov

iOS: Native

Screen.Recording.2024-10-07.at.11.58.06.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-10-07.at.11.56.12.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-10-07.at.11.50.15.PM.mov

MacOS: Desktop

Screen.Recording.2024-10-07.at.11.52.42.PM.mov

grgia · 2024-10-07T15:21:51Z

    const mostRecentReportAction = reportActions.at(0);
+    const isMostRecentReportIOU = mostRecentReportAction?.actionName === CONST.REPORT.ACTIONS.TYPE.IOU;
+    const isSingleIOUReportAction = reportActions.filter((action) => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU).length === 1;
+    const isSingleExpenseReport = ReportUtils.isExpenseReport(report) && isMostRecentReportIOU && isSingleIOUReportAction;
+    const isSingleInvoiceReport = ReportUtils.isInvoiceReport(report) && isMostRecentReportIOU && isSingleIOUReportAction;
    const shouldShowMostRecentReportAction =
        !!mostRecentReportAction &&


It seems like this case would have already been caught by the !!mostRecentReportAction check, could you elaborate why it wasn't?

@grgia I'm confused a little, could you please clarify how it would have been caught by the !!mostRecentReportAction check? You can also take a look at my proposal, I've tried to describe everything there in details.

isMostRecentReportIOU is mostRecentReportAction && is IOU

isSingleExpenseReport and isSingleInvoiceReport both also include the check isMostRecentReportIOU

so I'd think they would have been caught by the !!mostRecentReportAction.

Am I misreading the code?

Hm, but as you mentioned the isMostRecentReportIOU also includes the check for IOU report action type, and that's the main part of this check.

allroundexperts · 2024-10-07T19:06:40Z

Found a console warning while testing and reported it here

VickyStash · 2024-10-08T15:07:48Z

@allroundexperts @grgia Do you have any more questions regarding the PR? Any ETA on the review?

allroundexperts · 2024-10-08T15:40:43Z

@allroundexperts @grgia Do you have any more questions regarding the PR? Any ETA on the review?

Looks good from my end.

allroundexperts

Looks good to me!

VickyStash · 2024-10-09T13:15:38Z

@grgia kind bump here 🙂

OSBotify · 2024-10-09T16:10:49Z

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

github-actions · 2024-10-09T20:47:35Z

🚀 Deployed to staging by https://github.com/grgia in version: 9.0.47-1 🚀

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

github-actions · 2024-10-10T23:02:46Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.47-4 🚀

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

Fix one-expense report loading

2df50c5

VickyStash mentioned this pull request Oct 3, 2024

[HOLD for payment 2024-10-17] Expense preview disappear entirely clicking on one export report for a while #49853

Closed

6 tasks

mountiny requested a review from allroundexperts October 7, 2024 13:13

mountiny assigned VickyStash Oct 7, 2024

VickyStash changed the title ~~[WIP] Fix one-expense report loading~~ Fix one-expense report loading Oct 7, 2024

VickyStash marked this pull request as ready for review October 7, 2024 13:17

VickyStash requested a review from a team as a code owner October 7, 2024 13:17

melvin-bot Bot requested review from grgia and removed request for a team October 7, 2024 13:17

grgia reviewed Oct 7, 2024

View reviewed changes

allroundexperts approved these changes Oct 8, 2024

View reviewed changes

melvin-bot Bot requested a review from grgia October 8, 2024 15:41

grgia approved these changes Oct 9, 2024

View reviewed changes

grgia merged commit 81e914a into Expensify:main Oct 9, 2024

github-actions Bot mentioned this pull request Oct 9, 2024

Deploy Checklist: New Expensify 2024-10-09 #50518

Closed

58 tasks

Uh oh!

Conversation

VickyStash commented Oct 3, 2024 • 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!

melvin-bot Bot commented Oct 7, 2024

Uh oh!

allroundexperts commented Oct 7, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

grgia Oct 7, 2024

Choose a reason for hiding this comment

Uh oh!

VickyStash Oct 7, 2024

Choose a reason for hiding this comment

Uh oh!

grgia Oct 7, 2024

Choose a reason for hiding this comment

Uh oh!

VickyStash Oct 7, 2024

Choose a reason for hiding this comment

Uh oh!

allroundexperts commented Oct 7, 2024

Uh oh!

VickyStash commented Oct 8, 2024

Uh oh!

allroundexperts commented Oct 8, 2024

Uh oh!

allroundexperts left a comment

Choose a reason for hiding this comment

Uh oh!

VickyStash commented Oct 9, 2024

Uh oh!

OSBotify commented Oct 9, 2024

Uh oh!

github-actions Bot commented Oct 9, 2024

Uh oh!

github-actions Bot commented Oct 10, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

VickyStash commented Oct 3, 2024 •

edited

Loading

allroundexperts commented Oct 7, 2024 •

edited

Loading