Skip to content

Improve task and trip related list components performance#63686

Merged
mjasikowski merged 15 commits intoExpensify:mainfrom
hoangzinh:fix/63636-Improve-task-and-trip-performance
Jun 13, 2025
Merged

Improve task and trip related list components performance#63686
mjasikowski merged 15 commits intoExpensify:mainfrom
hoangzinh:fix/63636-Improve-task-and-trip-performance

Conversation

@hoangzinh
Copy link
Copy Markdown
Contributor

@hoangzinh hoangzinh commented Jun 6, 2025

Explanation of Change

Improve ReportActionsList performance by moving useOnyx connections from task and trip components up to the list level:

TaskAction.tsx => Do nothing
TaskPreview.tsx => lift up taskReport
TaskView.tsx => lift up parentReport
TripDetailsView.tsx => Do nothing
TripRoomPreview.tsx => lift up chatReport

Fixed Issues

$ #63636
PROPOSAL:

Tests

Same as QA

  • Verify that no errors appear in the JS console

Offline tests

Same as QA

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Test 1: Tasks

  1. Sign in to account A on main testing device
  2. Sign in to account B on 2nd testing device
  3. [Account B] assign a task for account A
  4. [Account A] Verify the task is displayed as normal
  5. [Account B] Change the task name
  6. [Account A] Verify the task name is updated in chat report
  7. [Account A] Click on checkbox to complete the task
  8. [Account A] Verify the task is marked as completed
  9. [Account A] Tap on the task to go to task view page
  10. [Account A] Verify it displays task as normal

Test 2: Trip
Precondition:

  1. Sign in an account has to Travel
  2. FAB -> Book travel
  3. Book any hotel/flight on Spotnana

Steps

  1. Sign in to the account above
  2. Go to Expense Workspace chat
  3. Verify App displays your bookings above as normal
  • 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: 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 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 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.ts 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 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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.

Screenshots/Videos

Android: Native
Screen.Recording.2025-06-10.at.09.07.01.android.mov
Android: mWeb Chrome
Screen.Recording.2025-06-10.at.09.11.55.android.chrome.mov
iOS: Native
Screen.Recording.2025-06-10.at.09.20.57.mov
iOS: mWeb Safari
Screen.Recording.2025-06-10.at.09.13.49.ios.safari.mov
MacOS: Chrome / Safari
Screen.Recording.2025-06-09.at.05.40.32.web.mov
MacOS: Desktop
Screen.Recording.2025-06-09.at.05.45.13.desktop.mov

@hoangzinh
Copy link
Copy Markdown
Contributor Author

hoangzinh commented Jun 8, 2025

Chat report has TaskPreview

=== 📁 Trace File Analysis ===

📄 File: profiling-data.06-08-2025.00-27-21.json
  • Commit count: 33
  • Total render duration: 732.000 ms
  • p50 / p95 / p99 (ms):
    • p50: 2.400 ms
    • p95: 123.500 ms
    • p99: 296.400 ms

📄 File: profiling-data.06-08-2025.07-17-05.json
  • Commit count: 32
  • Total render duration: 660.700 ms
  • p50 / p95 / p99 (ms):
    • p50: 1.300 ms
    • p95: 120.400 ms
    • p99: 297.200 ms

=== 📊 Trace Comparison ===

🔁 Comparing Baseline ↔️ profiling-data.06-08-2025.07-17-05.json
  🟢 Duration Diff: -71.300 ms
  🟢 Commit Count Diff: -1

Screenshot 2025-06-08 at 07 18 54

@hoangzinh
Copy link
Copy Markdown
Contributor Author

hoangzinh commented Jun 8, 2025

Chat report has TaskView

=== 📁 Trace File Analysis ===

📄 File: profiling-data.06-08-2025.13-48-48.json
  • Commit count: 34
  • Total render duration: 668.400 ms
  • p50 / p95 / p99 (ms):
    • p50: 2.200 ms
    • p95: 178.200 ms
    • p99: 219.000 ms

📄 File: profiling-data.06-08-2025.13-50-53.json
  • Commit count: 32
  • Total render duration: 666.400 ms
  • p50 / p95 / p99 (ms):
    • p50: 3.100 ms
    • p95: 170.500 ms
    • p99: 219.700 ms

=== 📊 Trace Comparison ===

🔁 Comparing Baseline ↔️ profiling-data.06-08-2025.13-50-53.json
  🟢 Duration Diff: -2.000 ms
  🟢 Commit Count Diff: -2

Screenshot 2025-06-08 at 13 51 20

@hoangzinh
Copy link
Copy Markdown
Contributor Author

hoangzinh commented Jun 8, 2025

Chat report has TripRoomReview


=== 📁 Trace File Analysis ===

📄 File: profiling-data.06-09-2025.05-23-14.json
  • Commit count: 32
  • Total render duration: 728.500 ms
  • p50 / p95 / p99 (ms):
    • p50: 2.300 ms
    • p95: 189.400 ms
    • p99: 245.500 ms

📄 File: profiling-data.06-09-2025.05-19-48.json
  • Commit count: 30
  • Total render duration: 542.200 ms
  • p50 / p95 / p99 (ms):
    • p50: 2.900 ms
    • p95: 107.400 ms
    • p99: 242.500 ms

=== 📊 Trace Comparison ===

🔁 Comparing Baseline ↔️ profiling-data.06-09-2025.05-19-48.json
  🟢 Duration Diff: -186.300 ms
  🟢 Commit Count Diff: -2

Screenshot 2025-06-09 at 05 24 04

@hoangzinh hoangzinh marked this pull request as ready for review June 8, 2025 22:50
@hoangzinh hoangzinh requested a review from a team as a code owner June 8, 2025 22:50
@melvin-bot melvin-bot bot requested a review from Pujan92 June 8, 2025 22:50
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Jun 8, 2025

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

@melvin-bot melvin-bot bot removed the request for review from a team June 8, 2025 22:50
@hoangzinh
Copy link
Copy Markdown
Contributor Author

Hey @Pujan92, @adhorodyski and @TMisiukiewicz

I still need to complete recordings as part of PR checklist. But this PR is ready for initial reviews

@hoangzinh
Copy link
Copy Markdown
Contributor Author

The eslint failed due to CONST.BETAS.TABLE_REPORT_VIEW will be fixed here #63533. We can ignore those type errors in this PR.

@hoangzinh
Copy link
Copy Markdown
Contributor Author

@Pujan92 @adhorodyski @TMisiukiewicz this PR is ready for next review round

@TMisiukiewicz
Copy link
Copy Markdown
Contributor

@hoangzinh left a couple of more comments, I think these are the last ones 🥇

({item: reportAction, index}: ListRenderItemInfo<OnyxTypes.ReportAction>) => {
return (
<ReportActionsListItemRenderer
allReports={allReports}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@adhorodyski @TMisiukiewicz Isn't passing allReports to all report action children will increase the memory usage?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think it won't. Because it's gonna pass a reference variable (point to a same memory allocated)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ah, Ok.

@hoangzinh
Copy link
Copy Markdown
Contributor Author

cc @Pujan92 for review

@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Jun 12, 2025

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: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • 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: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2025-06-12.at.17.59.17.mov
Screen.Recording.2025-06-12.at.18.03.52.mov
Screen.Recording.2025-06-12.at.18.05.04.mov
MacOS: Desktop

Copy link
Copy Markdown
Contributor

@Pujan92 Pujan92 left a comment

Choose a reason for hiding this comment

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

Codewise looks good, I am yet to add recordings due to failure in builds.

@melvin-bot melvin-bot bot requested a review from mjasikowski June 12, 2025 17:12
@Pujan92
Copy link
Copy Markdown
Contributor

Pujan92 commented Jun 12, 2025

@hoangzinh we need to resolve conflicts

@hoangzinh
Copy link
Copy Markdown
Contributor Author

I resolved the conflict @Pujan92

@mjasikowski mjasikowski merged commit cfa3ffc into Expensify:main Jun 13, 2025
17 checks passed
@OSBotify
Copy link
Copy Markdown
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.

@github-actions
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.1.67-0 🚀

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

@github-actions
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.1.67-2 🚀

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

const {translate} = useLocalize();
const theme = useTheme();
const [taskReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${taskReportID}`, {canBeMissing: true});
const taskReportID = taskReport?.reportID;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

there was a regression #64292, if taskReport is undefined user will be redirected to no found page

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.

7 participants