Reduce mapToTransactionItemWithAdditionalInfo invocations by szymonzalarski98 · Pull Request #76339 · Expensify/App

szymonzalarski98 · 2025-11-30T15:03:54Z

Explanation of Change

Fixed Issues

$ #76417
PROPOSAL:

Tests

Open Reports screen and check if everything works properly.
Select some reports and check if it works.
Verify if exporting selected elements works.
Try some filters, for instance change status field to approved and check if proper reports are displayed.

Offline tests

QA Steps

Same as tests

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
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 new assets were added or existing ones were modified, I verified that:
- The assets are optimized and compressed (for SVG files, run npm run compress-svg)
- The assets load correctly across all supported platforms.
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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2025-11-30T15:13:43Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...ponents/Search/SearchList/BaseSearchList/index.tsx	`0.00% <0.00%> (ø)`
src/components/Search/index.tsx	`33.00% <50.00%> (+0.46%)`	⬆️
src/components/Search/SearchList/index.tsx	`3.44% <0.00%> (+0.27%)`	⬆️
... and 429 files with indirect coverage changes

melvin-bot · 2025-12-02T16:13:54Z

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

szymonzalarski98 · 2025-12-02T16:15:10Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.
Files with missing lines Coverage Δ
...ponents/Search/SearchList/BaseSearchList/index.tsx 0.00% <0.00%> (ø)
src/components/Search/index.tsx 34.51% <0.00%> (+0.50%) ⬆️
src/components/Search/SearchList/index.tsx 2.70% <0.00%> (-0.69%) ⬇️
... and 177 files with indirect coverage changes

In my opinion it's ok, but if we need more test coverage I can prepare test file.

JmillsExpensify

No product review required.

dominictb · 2025-12-08T15:45:38Z

@szymonzalarski98 I think all the PERF-1 violations above are valid. Can you try to resolve them? Maybe pre-compute the itemsWithSelection list in a useMemo and reuse it in renderItem.

dominictb · 2025-12-08T15:48:56Z

+                        let allNonDeletedSelected = true;
+                        let hasNonDeletedTransactions = false;


I guess these are intentional for performance reason, right? Because we can directly filter the pending delete then count the selected.

I did some improvements, thank you for the comment

dominictb · 2025-12-08T15:52:27Z

I remember that we used to show the expense reports list in an collapsible format (the expense report row shows all of its expenses) but now we only show the expense report, then need to tap that row to view the expenses. @szymonzalarski98 Do you have any idea where it goes or did we get rid of it 😄 ?

…ng-map-to-transaction-item-computations

szymonzalarski98 · 2025-12-16T16:22:32Z

I remember that we used to show the expense reports list in an collapsible format (the expense report row shows all of its expenses) but now we only show the expense report, then need to tap that row to view the expenses. @szymonzalarski98 Do you have any idea where it goes or did we get rid of it 😄 ?

Sorry for late response, I'm quite new to the project, so sorry but I cannot give you a good answer :D

…ng-map-to-transaction-item-computations

dominictb · 2025-12-22T10:13:53Z

@szymonzalarski98 You mistakenly pushed Mobile-Expensify folder. Also we have conflicts.

szymonzalarski98 · 2025-12-23T16:54:55Z

@szymonzalarski98 You mistakenly pushed Mobile-Expensify folder. Also we have conflicts.

Thank you, I've removed it

dominictb · 2025-12-29T10:10:36Z

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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
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 there are no new alerts related to the canBeMissing param for useOnyx
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 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.ts 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.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Screen.Recording.2025-12-29.at.17.38.01.mov

Android: mWeb Chrome

iOS: HybridApp

Screen.Recording.2025-12-29.at.17.29.18-compressed.mov

iOS: mWeb Safari

Screen.Recording.2025-12-29.at.17.33.20.mov

MacOS: Chrome / Safari

Screen.Recording.2025-12-29.at.17.10.56.mov

Screen.Recording.2025-12-29.at.17.11.11.mov

Screen.Recording.2025-12-29.at.17.13.43.mov

dominictb

🎀

@szymonzalarski98 Can you add brief details to the Explanation of Change section so Product guys can have more context?

dominictb · 2025-12-29T10:17:57Z

+                        const mappedTransactions = item.transactions.map((transaction) => {
+                            const isTransactionSelected = !!(transaction.keyForList && selectedTransactions[transaction.keyForList]?.isSelected);
+
+                            if (transaction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE) {


Suggested change

if (transaction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE) {

if (isTransactionPendingDelete(transaction)) {

OSBotify · 2025-12-29T11:54:23Z

✋ 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 · 2025-12-29T12:30:38Z

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.2.88-0 🚀

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

OSBotify · 2025-12-30T14:57:52Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.88-7 🚀

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

melvin-bot Bot assigned szymonzalarski98 Nov 30, 2025

szymonzalarski98 force-pushed the callstack-internal/szymonzalarski/reports/long-map-to-transaction-item-computations branch from 346fef0 to 2e4e6c4 Compare November 30, 2025 15:05

mountiny mentioned this pull request Dec 1, 2025

[Due for payment 2026-01-06] [$250] Eliminate UI Jank on Search Page Filtering #76417

Closed

Reduce mapToTransactionItemWithAdditionalInfo invocations

09f2f8d

szymonzalarski98 force-pushed the callstack-internal/szymonzalarski/reports/long-map-to-transaction-item-computations branch from 2e4e6c4 to 09f2f8d Compare December 2, 2025 15:26

szymonzalarski98 marked this pull request as ready for review December 2, 2025 16:13

szymonzalarski98 requested review from a team as code owners December 2, 2025 16:13

melvin-bot Bot requested review from JmillsExpensify and dominictb and removed request for a team December 2, 2025 16:13

melvin-bot Bot removed the request for review from a team December 2, 2025 16:13