Skip to content

Revert "use useSearchSelector hook and remove unused and duplicated code"#74302

Merged
luacmartins merged 1 commit intomainfrom
revert-71427-mkzie2-issue/71061
Nov 5, 2025
Merged

Revert "use useSearchSelector hook and remove unused and duplicated code"#74302
luacmartins merged 1 commit intomainfrom
revert-71427-mkzie2-issue/71061

Conversation

@lakchote
Copy link
Contributor

@lakchote lakchote commented Nov 5, 2025

@lakchote lakchote requested review from a team as code owners November 5, 2025 10:20
@melvin-bot melvin-bot bot requested review from MonilBhavsar and joekaufmanexpensify and removed request for a team November 5, 2025 10:20
@melvin-bot
Copy link

melvin-bot bot commented Nov 5, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

🚧 @lakchote has triggered a test Expensify/App build. You can view the workflow run here.

const initialSelectedOptions = useMemo(() => {
return value.reduce<OptionData[]>((acc, id) => {
const participant = personalDetails?.[id];
if (!participant) {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useMemo hook depends on the entire personalDetails object. Changes to any property will trigger re-computation even when only specific properties are needed.

Instead, extract and depend on only the specific properties required:

const initialSelectedOptions = useMemo(() => {
    return value.reduce<OptionData[]>((acc, id) => {
        const participant = personalDetails?.[id];
        if (!participant) {
            return acc;
        }
        // ... rest of logic
    }, []);
}, [value, ...value.map(id => personalDetails?.[id])]); // or extract needed keys

countryCode,
);
}, [options.reports, options.personalDetails, draftComments, countryCode]);

Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useMemo depends on entire objects availableOptions.personalDetails and availableOptions.recentReports. Changes to any property in these arrays will trigger re-computation unnecessarily.

Consider extracting specific properties needed or using more granular dependencies to prevent unnecessary recalculations when unrelated data changes.

@@ -117,11 +157,11 @@ function SearchFiltersParticipantsSelector({initialAccountIDs, onFiltersUpdate}:
sections: newSections,
headerMessage: message,
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useEffect depends on the entire personalDetails object. It will re-execute whenever any property in personalDetails changes, even if the changes are unrelated to the initialAccountIDs.

Extract and depend on only the specific personal detail entries needed:

// eslint-disable-next-line react-compiler/react-compiler, react-hooks/exhaustive-deps
}, [initialAccountIDs, ...initialAccountIDs.map(id => personalDetails?.[id])]);

const [didScreenTransitionEnd, setDidScreenTransitionEnd] = useState(false);
const {contacts} = useContactImport();
const {options: listOptions, areOptionsInitialized} = useOptionsList({
shouldInitialize: didScreenTransitionEnd,
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useMemo depends on entire objects availableOptions and selectedOptions. Changes to any property will trigger re-computation unnecessarily.

Consider depending on specific properties that are actually used in the computation instead of the entire objects.

personalDetails: (listOptions.personalDetails ?? []).concat(contacts),
},
draftComments,
{
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useMemo depends on entire objects options.personalDetails, options.recentReports, options.userToInvite, and selectedOptions. Changes to any property in these objects will trigger unnecessary re-computation.

Depend on specific properties needed for the header message calculation instead of entire objects.

undefined,
reportAttributesDerived,
);
sectionsList.push(formatResults.section);
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

This useMemo depends on entire objects selectedOptions, recentReports, personalDetails, and reportAttributesDerived. Changes to any property in these objects will trigger re-computation of sections unnecessarily.

Extract and depend on specific properties needed for section construction to prevent unnecessary recalculations.

return filteredOptions;
}, [unselectedOptions, cleanSearchTerm, selectedOptions, countryCode]);

const {sections, headerMessage} = useMemo(() => {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-4 (docs)

This code creates new object instances with spread operator on every render inside the useMemo for sections. While the sections array itself is memoized, the .map() creates new object references for each option on every computation.

Consider memoizing the transformed data or ensure this transformation only happens when the underlying data actually changes by having more specific dependencies in the parent useMemo.

@codecov
Copy link

codecov bot commented Nov 5, 2025

Codecov Report

❌ Patch coverage is 16.47059% with 71 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...nents/Search/SearchFiltersParticipantsSelector.tsx 0.00% 39 Missing ⚠️
...ponents/Search/FilterDropdowns/UserSelectPopup.tsx 0.00% 19 Missing ⚠️
src/hooks/useSearchSelector.base.ts 7.69% 12 Missing ⚠️
src/pages/NewChatPage.tsx 92.85% 1 Missing ⚠️
Files with missing lines Coverage Δ
src/pages/NewChatPage.tsx 78.88% <92.85%> (+1.38%) ⬆️
src/hooks/useSearchSelector.base.ts 53.44% <7.69%> (-26.56%) ⬇️
...ponents/Search/FilterDropdowns/UserSelectPopup.tsx 0.00% <0.00%> (ø)
...nents/Search/SearchFiltersParticipantsSelector.tsx 0.00% <0.00%> (ø)

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

@lakchote lakchote changed the title Revert "use useSearchSelector hook and remove unused and duplicated code" [HOLD] Revert "use useSearchSelector hook and remove unused and duplicated code" Nov 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #74302.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/74302/index.html ⏩ SKIPPED ⏩
Android The build for iOS was skipped
Desktop 💻 Web 🕸️
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Desktop was skipped The build for Web was skipped

👀 View the workflow run that generated this build 👀

Copy link
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

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

👍

@joekaufmanexpensify
Copy link
Contributor

No product considerations. Removing my review and unsubscribing

@joekaufmanexpensify joekaufmanexpensify removed their request for review November 5, 2025 14:47
@luacmartins luacmartins changed the title [HOLD] Revert "use useSearchSelector hook and remove unused and duplicated code" Revert "use useSearchSelector hook and remove unused and duplicated code" Nov 5, 2025
@luacmartins
Copy link
Contributor

luacmartins commented Nov 5, 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 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

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@luacmartins
Copy link
Contributor

Straight revert, gonna merge without checklists and with the failing ESLint test

@luacmartins luacmartins merged commit 4ad44ed into main Nov 5, 2025
27 of 38 checks passed
@luacmartins luacmartins deleted the revert-71427-mkzie2-issue/71061 branch November 5, 2025 15:02
@melvin-bot
Copy link

melvin-bot bot commented Nov 5, 2025

@luacmartins looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@melvin-bot melvin-bot bot added the Emergency label Nov 5, 2025
OSBotify pushed a commit that referenced this pull request Nov 5, 2025
Revert "use useSearchSelector hook and remove unused and duplicated code"

(cherry picked from commit 4ad44ed)

(cherry-picked to staging by luacmartins)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Nov 5, 2025
@OSBotify
Copy link
Contributor

OSBotify commented Nov 5, 2025

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.2.44-2 🚀

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

@Beamanator
Copy link
Contributor

FYI #72318 is a backend thing, not related to the reverted PR 👍

@luacmartins
Copy link
Contributor

Ah thanks for pointing that out

@OSBotify
Copy link
Contributor

OSBotify commented Nov 5, 2025

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.44-5 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Nov 5, 2025

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.2.45-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Nov 6, 2025

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.45-6 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants