Skip to content

Perf/spend filters hover - #97697

Draft
sumo-slonik wants to merge 2 commits into
Expensify:mainfrom
software-mansion-labs:perf/spend-filters-hover
Draft

Perf/spend filters hover#97697
sumo-slonik wants to merge 2 commits into
Expensify:mainfrom
software-mansion-labs:perf/spend-filters-hover

Conversation

@sumo-slonik

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

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

  • 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
  • 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 followed proper code patterns (see Reviewing the code)
    • 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 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)
  • 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)
  • 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.
  • 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

…lectors

Cache the wrapped snapshot selector per (selector, key) so Onyx keeps memoizing
its result instead of re-running the selector over the whole collection on every
render. Memoize the three remaining full passes over the personal details list
(createOptionList, getValidOptions, the list data copy in UserSelector) with a
comparator that walks one level into rebuilt record arguments, keep the Onyx
subscriptions warm for the lifetime of the filters popover, and defer the filter
content render so passing the cursor over a filter no longer mounts it.
…mand

Switch the filter content of the advanced filters popover to a hover-intent
delay so a filter the cursor only passes over never becomes the content key, and
keep the filters that were actually shown mounted behind Activity, so returning
to one is a visibility toggle instead of a rebuild of its option list. Size the
option-list caches for the four user filters now that those are mounted side by
side.

Load the seven heaviest filter selectors on demand and warm them up when a
filters popover opens, so the Search page no longer carries the option list,
selection list, card, accounting and report name helpers for a user who never
opens a filter.

Cache the collection slices of the search snapshot per snapshot object, so the
45 collection reads on Search each walk it once between updates instead of once
per subscriber. Narrow the chip subscriptions down to what each one renders: the
report names of the selected reports, a dedicated context for the results error
flag, and set lookups instead of scanning the selected values per entry. Sort
the tag, category and currency chip values into a copy, since the array behind
them comes straight out of the Onyx cache.
@codecov

codecov Bot commented Aug 3, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 94.81% <ø> (ø)
...omponents/Search/FilterComponents/UserSelector.tsx 96.87% <100.00%> (+0.44%) ⬆️
...nents/Search/FilterDropdowns/FilterPopupButton.tsx 100.00% <100.00%> (ø)
src/components/Search/SearchContext.tsx 100.00% <100.00%> (ø)
src/components/Search/SearchContextDefinitions.ts 55.17% <100.00%> (+3.32%) ⬆️
...ts/Search/SearchPageHeader/useSearchFiltersBar.tsx 24.61% <100.00%> (+1.17%) ⬆️
src/components/Search/SearchResultsProvider.tsx 78.57% <100.00%> (+1.64%) ⬆️
src/hooks/usePersonalDetailOptions.ts 62.90% <100.00%> (+0.60%) ⬆️
src/hooks/usePersonalDetailSearchSelector/base.ts 96.20% <100.00%> (+0.31%) ⬆️
src/libs/PolicyUtils.ts 77.34% <100.00%> (+0.07%) ⬆️
... and 11 more
... and 90 files with indirect coverage changes

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.

1 participant