[Lint] Replace PERF-5 ai reviewer rule with `no-deep-equal-in-memo` eslint equivalent by kacper-mikolajczak · Pull Request #76364 · Expensify/App

kacper-mikolajczak · 2025-12-01T09:53:31Z

Explanation of Change

Fixed Issues

$ #76362
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Money Request Flow (affected: `MoneyRequestConfirmationList`, `MoneyRequestConfirmationListFooter`)

Steps:

Open the app and navigate to a chat or workspace
Tap the + button and select Submit expense
Enter an amount (e.g., $50)
Add a merchant name
Select a category (if available)
Verify all fields display correctly on the confirmation screen
Submit the expense
Expected: Expense is created successfully with all entered details

2. Report Screen (affected: `ReportScreen`, `ReportFooter`)

Steps:

Open an existing expense report or chat
Scroll through the report history
Send a new message in the chat
Verify the message appears correctly
Navigate away and return to the report
Expected: Report loads correctly, messages display properly, no flickering or UI glitches

3. Report Action Items (affected: `PureReportActionItem`, `ReportActionItemContentCreated`)

Steps:

Open a report with multiple action items (expenses, messages, etc.)
Scroll through the report actions
Long-press on a message to open the context menu
Select an action (e.g., copy, reply, edit)
Expected: Context menu works correctly, actions perform as expected

4. Context Menu (affected: `BaseReportActionContextMenu`)

Steps:

Open any chat/report
Long-press on different types of messages (text, expense, system message)
Verify context menu appears with appropriate options
Select various menu items
Expected: Context menu displays correctly with proper options for each message type

5. Popover Menu (affected: `PopoverMenu`)

Steps:

Navigate to various screens that use popover menus (e.g., workspace settings, FAB menu)
Open and close popover menus multiple times
Select menu items
Expected: Popover menus animate correctly and function properly

6. Option Row / Participant Selection (affected: `OptionRow`, `MoneyRequestParticipantsSelector`, `MoneyRequestAttendeeSelector`)

Attendee selection:

Create a per diem or expense with attendees (if available)
Add/remove attendees
Expected: Attendee list updates correctly

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

github-actions · 2025-12-01T09:53:41Z

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

codecov · 2025-12-01T10:02:51Z

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 Δ
.../components/MoneyRequestConfirmationListFooter.tsx	`84.30% <100.00%> (ø)`
src/components/PopoverMenu.tsx	`79.45% <ø> (ø)`
src/pages/home/ReportScreen.tsx	`68.84% <ø> (ø)`
...report/ContextMenu/BaseReportActionContextMenu.tsx	`0.00% <ø> (ø)`
src/pages/home/report/PureReportActionItem.tsx	`52.64% <ø> (ø)`
src/pages/home/report/ReportFooter.tsx	`52.17% <100.00%> (ø)`
...pages/iou/request/MoneyRequestAttendeeSelector.tsx	`0.00% <ø> (ø)`
...s/iou/request/MoneyRequestParticipantsSelector.tsx	`0.00% <ø> (ø)`
src/components/OptionRow.tsx	`1.02% <0.00%> (-0.02%)`	⬇️
...ges/home/report/ReportActionItemContentCreated.tsx	`26.66% <50.00%> (ø)`
... and 1 more
... and 12 files with indirect coverage changes

kacper-mikolajczak · 2025-12-01T10:30:00Z

Update:

Tests are failing due to invalid date.
Eslint checks caught usages of deepEqual, however they need C+ validation whether they can be replaced with shallow comparison (===)

@mountiny marking this as ready for review in order to get the feedback from C+

melvin-bot · 2025-12-01T10:33:18Z

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

kacper-mikolajczak · 2025-12-01T10:36:31Z

Hi @brunovjk, this PR introduces new eslint rule which prohibits deepEquals usage in React.memo.

After runnig linter, there are couple of components found that violates this, however I don't have full confidence whether they are correct and should be left intact or they can be replaced with shallow comparisons.

Please take a look at eslint output and share your thoughts on above. Thanks! ❤️

brunovjk · 2025-12-02T21:07:54Z

@kacper-mikolajczak — nice work, I think we shouldn’t blindly replace every deepEqual. I suggest a per-instance triage:

If the compare function only checks primitives or stable refs, I think a shallow === (or default React.memo) is safe.
If nested objects/arrays are compared and their internal values matter, I think we should either keep the deepEqual, or refactor to pass stable refs (useMemo/useCallback) or compare only the specific nested fields.
For uncertain cases I think we should keep deepEqual for now and add a short code comment (or eslint-disable-next-line with a TODO) to audit later.

Make sense? Thank you.

kacper-mikolajczak · 2025-12-04T11:28:23Z

@brunovjk I find approach like that feasible for this PR, thanks!

I have implemented all the desired changes:

replaced deepEqual with shallow check when possible
for uncertain scenarios, I left deepEqual and disabled lint rule

Let me know what you think of introduced changes.

kacper-mikolajczak · 2025-12-04T20:52:02Z

@brunovjk the Changed files ESlint check failed, even though full eslint check has passed. This two seem to be contradictive. Can we re-run failing job?

Apart from that, PR is ready for further review.

JmillsExpensify

No product review required.

brunovjk · 2025-12-05T21:07:11Z

src/pages/home/report/PureReportActionItem.tsx

@@ -1,3 +1,4 @@
+/* eslint-disable rulesdir/no-deep-equal-in-memo */


Why disable the rule at the beginning of the file? Thank you.

Otherwise, we'd need to disable in multiple lines. Let me know what is the recommended approach here, thanks!

I think ideally we disable it in the lines individually as then nobody will be forced to observe this rule in this file after that

brunovjk · 2025-12-05T21:07:28Z

src/pages/home/report/ReportActionItemContentCreated.tsx

-        deepEqual(prevProps.contextValue, nextProps.contextValue) &&
-        deepEqual(prevProps.parentReportAction, nextProps.parentReportAction) &&
+        prevProps.contextValue === nextProps.contextValue &&
+        prevProps.parentReport === nextProps.parentReport &&


@kacper-mikolajczak you changed the prop here from parentReportAction to parentReport, sorry, but was that intentional? Thank you.

That was not intended at all. Thanks for spotting this one out ❤️ Fixed ✅

brunovjk · 2025-12-05T21:08:09Z

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

Uploading 76364_android_native.mov…

Android: mWeb Chrome

Uploading 76364_android_web.mov…

iOS: HybridApp

76364_ios_native.mov

iOS: mWeb Safari

Uploading 76364_ios_web.mov…

MacOS: Chrome / Safari

76364_web_chrome.mov

brunovjk · 2025-12-05T21:09:19Z

@kacper-mikolajczak Won't we need QA here? To ensure that none of these latest changes introduce regressions. Thank you.

mountiny · 2025-12-06T10:39:44Z

+1 lets try to write test steps for these cases

roryabraham · 2025-12-11T23:10:34Z

package.json

    "eslint": "^9.36.0",
    "eslint-config-airbnb-typescript": "^18.0.0",
-    "eslint-config-expensify": "2.0.100",
+    "eslint-config-expensify": "github:Expensify/eslint-config-expensify#0432ea0ed4da293811502d6aabc60190d24ad1ad",


Why'd you change this to a GitHub ref? Was there some problem with the npm-published version?

Thanks Rory! ❤️ Resolving it in a moment

That was for testing of the total lint time on the PR 🙌

mountiny · 2025-12-15T11:42:18Z

Can you also please check the failing gh action please?

kacper-mikolajczak · 2025-12-15T15:11:45Z

Can you also please check the failing gh action please?

Sure, checking this after merging latest main and bumping up linter.

roryabraham · 2025-12-15T20:58:08Z

package.json

    "eslint": "^9.36.0",
    "eslint-config-airbnb-typescript": "^18.0.0",
-    "eslint-config-expensify": "2.0.100",
+    "eslint-config-expensify": "^2.0.101",


Whoops, please don't use the ^:

Suggested change

"eslint-config-expensify": "^2.0.101",

"eslint-config-expensify": "2.0.101",

We don't use proper semver in most of our dependencies, meaning that we almost never want ^ because it makes it so that we might unintentionally upgrade the dependency to anything less than 3.0. I don't understand why this is such a popular practice, as it also just makes it much less clear what package version is actually installed

Agree on that one! I think it goes back to how npm i by default allows minor/patch bumps and it often slips past when doing quick changes. Thanks for spotting this ❤️

@roryabraham To avoid this in future, here's a quick fix for linter README: Expensify/eslint-config-expensify#173

Co-authored-by: Rory Abraham <47436092+roryabraham@users.noreply.github.com>

Coming from: Expensify/App#76364 (comment) We don't want devs to have different eslint configs installed by accident.

kacper-mikolajczak · 2025-12-16T09:01:17Z

@mountiny we've got this approved and ready - seems like failing ESLint check is caused by out of scope issue.

Let me know if we can merge this 🚀

mountiny

Thanks, the failing eslint changed is unrelated code to these changes to limit the scope we will skip that now

mountiny · 2025-12-16T09:39:57Z

src/pages/home/report/PureReportActionItem.tsx

@@ -1,3 +1,4 @@
+/* eslint-disable rulesdir/no-deep-equal-in-memo */


I think ideally we disable it in the lines individually as then nobody will be forced to observe this rule in this file after that

OSBotify · 2025-12-16T10:15: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-16T22:46:46Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.79-0 🚀

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

nlemma · 2025-12-17T09:42:20Z

@kacper-mikolajczak Is there a new way to add participants while creating expenses, step 6 from test 1 and step 2 from test 6 are a bit confusing. Could you please explain that for me, thanks.

OSBotify · 2025-12-17T12:24:28Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.81-0 🚀

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

kavimuru · 2025-12-17T16:16:29Z

@mountiny @kacper-mikolajczak @brunovjk
Please help with these:

Money Request Flow (affected: MoneyRequestConfirmationList, MoneyRequestConfirmationListFooter)
Add participants to split the expense

Option Row / Participant Selection (affected: OptionRow, MoneyRequestParticipantsSelector, MoneyRequestAttendeeSelector)
Steps:

Create a new expense
Add multiple participants by searching and selecting

Is there a new way to add participants while creating expenses, step 6 from test 1 and step 2 from test 6 are a bit confusing.

kacper-mikolajczak · 2025-12-18T09:41:21Z

Hi @kavimuru @nlemma 👋

Thanks for spotting this, it should be adjusted the same way incorrect steps reported before by Bruno. Removed unclear steps ✅

Sorry for the confusion!

OSBotify · 2025-12-18T18:45:57Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.81-5 🚀

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

OSBotify · 2025-12-18T21:09:21Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.81-5 🚀

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

package-lock.json

eslint rule

2ebb58e

melvin-bot bot assigned kacper-mikolajczak Dec 1, 2025

kacper-mikolajczak mentioned this pull request Dec 1, 2025

[Due for payment 2025-12-26] [Due for payment 2025-12-18] [AI Reviewer] PERF-5 eslint rewrite #76362

Closed

kacper-mikolajczak marked this pull request as ready for review December 1, 2025 10:33

kacper-mikolajczak requested a review from a team as a code owner December 1, 2025 10:33

melvin-bot bot requested review from brunovjk and removed request for a team December 1, 2025 10:33

fix deepEquals

9b26829

kacper-mikolajczak requested a review from a team as a code owner December 4, 2025 09:15

melvin-bot bot requested review from JmillsExpensify and removed request for a team December 4, 2025 09:15

fix deepEquals

f67a9e4

kacper-mikolajczak changed the title ~~[Lint] Replace PERF-5 ai reviewer rule with no-deep-equal-in-memo eslint equivalent~~ [NoQA][Lint] Replace PERF-5 ai reviewer rule with no-deep-equal-in-memo eslint equivalent Dec 4, 2025

kacper-mikolajczak added 2 commits December 4, 2025 11:55

remove deepEqual import

e3a3c2c

fix deepEquals

0bbde51

remove unused import

e8335df

JmillsExpensify reviewed Dec 4, 2025

View reviewed changes

brunovjk reviewed Dec 5, 2025

View reviewed changes

melvin-bot bot requested a review from mountiny December 11, 2025 20:52

roryabraham reviewed Dec 11, 2025

View reviewed changes

kacper-mikolajczak mentioned this pull request Dec 15, 2025

No deep equal check in memo rule Expensify/eslint-config-expensify#171

Merged

Merge branch 'main' into feat/replace-perf-5-rule-with-eslint

cce06cd

bump expensify eslint to 101

a3c436e

roryabraham approved these changes Dec 15, 2025

View reviewed changes

roryabraham requested changes Dec 15, 2025

View reviewed changes

Update package.json

23992a4

Co-authored-by: Rory Abraham <47436092+roryabraham@users.noreply.github.com>

kacper-mikolajczak mentioned this pull request Dec 16, 2025

Update npm install command to use -E flag Expensify/eslint-config-expensify#173

Merged

kacper-mikolajczak requested a review from roryabraham December 16, 2025 08:22

roryabraham approved these changes Dec 16, 2025

View reviewed changes

Merge branch 'main' into feat/replace-perf-5-rule-with-eslint

10708d8

mountiny approved these changes Dec 16, 2025

View reviewed changes

mountiny merged commit 1ffa9e4 into Expensify:main Dec 16, 2025
38 of 39 checks passed

OSBotify mentioned this pull request Dec 16, 2025

Deploy Checklist: New Expensify 2025-12-16 #77818

Closed

ikevin127 mentioned this pull request Dec 16, 2025

[NewFeature] Add ability to require attendees based on category selection #76687

Merged

53 tasks

mountiny mentioned this pull request Dec 17, 2025

[NoQA] Fix: eslint-config-expensify 2.0.101 bump #77864

Merged

53 tasks

situchan reviewed Dec 22, 2025

View reviewed changes

package-lock.json Show resolved Hide resolved

		@@ -1,3 +1,4 @@
		/* eslint-disable rulesdir/no-deep-equal-in-memo */

	"eslint-config-expensify": "^2.0.101",
	"eslint-config-expensify": "2.0.101",

Conversation

kacper-mikolajczak commented Dec 1, 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

1. Money Request Flow (affected: MoneyRequestConfirmationList, MoneyRequestConfirmationListFooter)

2. Report Screen (affected: ReportScreen, ReportFooter)

3. Report Action Items (affected: PureReportActionItem, ReportActionItemContentCreated)

4. Context Menu (affected: BaseReportActionContextMenu)

5. Popover Menu (affected: PopoverMenu)

6. Option Row / Participant Selection (affected: OptionRow, MoneyRequestParticipantsSelector, MoneyRequestAttendeeSelector)

PR Author Checklist

Screenshots/Videos

Uh oh!

github-actions bot commented Dec 1, 2025

Uh oh!

codecov bot commented Dec 1, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

kacper-mikolajczak commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

melvin-bot bot commented Dec 1, 2025

Uh oh!

kacper-mikolajczak commented Dec 1, 2025

Uh oh!

brunovjk commented Dec 2, 2025

Uh oh!

kacper-mikolajczak commented Dec 4, 2025

Uh oh!

kacper-mikolajczak commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

brunovjk commented Dec 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

brunovjk commented Dec 5, 2025

Uh oh!

mountiny commented Dec 6, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mountiny commented Dec 15, 2025

Uh oh!

kacper-mikolajczak commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kacper-mikolajczak commented Dec 16, 2025

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

kacper-mikolajczak commented Dec 1, 2025 •

edited

Loading

1. Money Request Flow (affected: `MoneyRequestConfirmationList`, `MoneyRequestConfirmationListFooter`)

2. Report Screen (affected: `ReportScreen`, `ReportFooter`)

3. Report Action Items (affected: `PureReportActionItem`, `ReportActionItemContentCreated`)

4. Context Menu (affected: `BaseReportActionContextMenu`)

5. Popover Menu (affected: `PopoverMenu`)

6. Option Row / Participant Selection (affected: `OptionRow`, `MoneyRequestParticipantsSelector`, `MoneyRequestAttendeeSelector`)

codecov bot commented Dec 1, 2025 •

edited by github-actions bot

Loading

kacper-mikolajczak commented Dec 1, 2025 •

edited

Loading

kacper-mikolajczak commented Dec 4, 2025 •

edited

Loading

brunovjk commented Dec 5, 2025 •

edited

Loading

kacper-mikolajczak commented Dec 15, 2025 •

edited

Loading