fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part by thelullabyy · Pull Request #73174 · Expensify/App

thelullabyy · 2025-10-22T05:22:49Z

Explanation of Change

Fix regression in #73081
We use useArchivedReportsIdSet in here

App/src/components/Search/index.tsx

Line 276 in c7b3a44

const archivedReportsIdSet = useArchivedReportsIdSet();

which is recalculate every time render leads to callback here in loop

App/src/components/Search/index.tsx

Line 378 in c7b3a44

const [data, dataLength] = useMemo(() => {

Fix: Adjust to useArchivedReportsIdSet not recalculate everytime

Fixed Issues

$#67103
PROPOSAL:

Tests

Open the app
Go to workspace chat.
Create an expense.
Go to Reports > Expenses.
Click Select all checkbox.
Click on any table header title (eg, Date, Merchant)
Verify app not crash and feature work properly

Verify that no errors appear in the JS console

Offline tests

QA Steps

Open the app
Go to workspace chat.
Create an expense.
Go to Reports > Expenses.
Click Select all checkbox.
Click on any table header title (eg, Date, Merchant)
Verify app not crash and feature work properly

Verify that no errors appear in the JS console

PR Author Checklist

Screen.Recording.2025-10-21.at.22.26.07.mov

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2025-10-22T06:01:04Z

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

codecov · 2025-10-22T06:01:19Z

Codecov Report

❌ Patch coverage is 54.83871% with 28 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/libs/actions/Report.ts	40.00%	6 Missing ⚠️
src/libs/actions/IOU.ts	44.44%	5 Missing ⚠️
...c/components/Search/SearchFiltersChatsSelector.tsx	0.00%	3 Missing ⚠️
src/hooks/useArchivedReportsIdSet.ts	72.72%	3 Missing ⚠️
.../pages/tasks/TaskShareDestinationSelectorModal.tsx	0.00%	2 Missing ⚠️
src/components/MoneyReportHeader.tsx	0.00%	1 Missing ⚠️
...nents/ReportActionItem/MoneyRequestReceiptView.tsx	0.00%	1 Missing ⚠️
src/components/Search/index.tsx	0.00%	1 Missing ⚠️
src/hooks/useSelectedTransactionsActions.ts	0.00%	1 Missing ⚠️
src/libs/Navigation/AppNavigator/AuthScreens.tsx	50.00%	1 Missing ⚠️
... and 4 more

Files with missing lines	Coverage Δ
...tachments/AttachmentCarousel/extractAttachments.ts	`70.83% <ø> (ø)`
src/components/MoneyRequestHeader.tsx	`0.62% <ø> (ø)`
...RequestReportView/MoneyRequestReportNavigation.tsx	`33.33% <ø> (+31.37%)`	⬆️
src/hooks/useIsReportReadyToDisplay.ts	`100.00% <ø> (ø)`
src/libs/DebugUtils.ts	`68.99% <ø> (-0.07%)`	⬇️
src/libs/QuickActionUtils.ts	`41.66% <ø> (-0.69%)`	⬇️
src/libs/ReportUtils.ts	`74.33% <100.00%> (+0.06%)`	⬆️
src/libs/SidebarUtils.ts	`80.58% <ø> (-0.05%)`	⬇️
src/pages/ReportDetailsPage.tsx	`58.33% <ø> (ø)`
src/pages/home/report/PureReportActionItem.tsx	`53.55% <ø> (ø)`
... and 15 more

... and 7 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

DylanDylann · 2025-10-22T06:17:48Z

@thelullabyy Please give an explanation on how we fix the regression

thelullabyy · 2025-10-22T06:20:26Z

@DylanDylann Added

DylanDylann · 2025-10-22T06:34:14Z

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
- 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 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

Screen.Recording.2025-10-21.at.22.22.38.mov

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

tgolen · 2025-10-22T15:44:59Z

src/hooks/useArchivedReportsIdSet.ts

+        },
+    });
+
+    return useDeepCompareRef(archivedReportsIdSet) ?? new Set<string>();


Can you please add a code comment here that explains why useDeepCompareRef is necessary?

@tgolen I added. Please check if it's clear enough

tgolen

Yeah, that looks great. Thank you!

OSBotify · 2025-10-22T16:29:44Z

✋ 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-10-23T13:11:26Z

🚀 Deployed to staging by https://github.com/tgolen in version: 9.2.37-1 🚀

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

OSBotify · 2025-10-24T17:53:37Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

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

refatore: remove getReportNameValuePairs final

4df272e

melvin-bot bot assigned thelullabyy Oct 22, 2025

thelullabyy changed the title ~~fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part~~ [NoQA] fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part Oct 22, 2025

update code

0240661

thelullabyy marked this pull request as ready for review October 22, 2025 06:00

thelullabyy requested a review from a team as a code owner October 22, 2025 06:00

melvin-bot bot requested review from DylanDylann and removed request for a team October 22, 2025 06:01

thelullabyy changed the title ~~[NoQA] fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part~~ fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part Oct 22, 2025

DylanDylann approved these changes Oct 22, 2025

View reviewed changes

melvin-bot bot requested a review from tgolen October 22, 2025 06:42

tgolen requested changes Oct 22, 2025

View reviewed changes

thelullabyy added 2 commits October 22, 2025 22:46

Merge branch 'main' into fix/67103-remove-getReportNameValuePairs-part-6

a88fdd7

refactor: add comment

c7fe8dc

tgolen approved these changes Oct 22, 2025

View reviewed changes

tgolen merged commit 14329cd into Expensify:main Oct 22, 2025
26 checks passed

OSBotify mentioned this pull request Oct 23, 2025

Deploy Checklist: New Expensify 2025-10-23 #73307

Closed

88 tasks

aldo-expensify mentioned this pull request Oct 23, 2025

[Due for payment 2025-11-03] Hold Expense - Not here page opens after deleting an expense. #73330

Closed

8 tasks

melvin-bot bot mentioned this pull request Oct 24, 2025

[$1500] [Due for payment 2025-10-31] Remove call to getReportNameValuePairs() in method canUserPerformWriteAction from ReportUtils.ts #67103

Closed

dominictb mentioned this pull request Jan 26, 2026

[NoQA] Remove useDeepCompareRef hook #78377

Merged

53 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part#73174

fix: remove getReportNameValuePairs in method canUserPerformWriteAction final part#73174
tgolen merged 4 commits intoExpensify:mainfrom
thelullabyy:fix/67103-remove-getReportNameValuePairs-part-6

thelullabyy commented Oct 22, 2025 •

edited

Loading

Uh oh!

melvin-bot bot commented Oct 22, 2025

Uh oh!

codecov bot commented Oct 22, 2025 •

edited

Loading

Uh oh!

DylanDylann commented Oct 22, 2025

Uh oh!

thelullabyy commented Oct 22, 2025

Uh oh!

DylanDylann commented Oct 22, 2025

Uh oh!

tgolen Oct 22, 2025

Uh oh!

thelullabyy Oct 22, 2025

Uh oh!

tgolen left a comment

Uh oh!

Uh oh!

OSBotify commented Oct 22, 2025

Uh oh!

OSBotify commented Oct 23, 2025

Uh oh!

OSBotify commented Oct 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

thelullabyy commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Oct 22, 2025

Uh oh!

codecov bot commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

DylanDylann commented Oct 22, 2025

Uh oh!

thelullabyy commented Oct 22, 2025

Uh oh!

DylanDylann commented Oct 22, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

tgolen Oct 22, 2025

Choose a reason for hiding this comment

Uh oh!

thelullabyy Oct 22, 2025

Choose a reason for hiding this comment

Uh oh!

tgolen left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Oct 22, 2025

Uh oh!

OSBotify commented Oct 23, 2025

Uh oh!

OSBotify commented Oct 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

thelullabyy commented Oct 22, 2025 •

edited

Loading

codecov bot commented Oct 22, 2025 •

edited

Loading