Skip to content

perf: share scans across useShortMentionsList instances - #96617

Merged
mountiny merged 7 commits into
Expensify:mainfrom
callstack-internal:perf/share-short-mentions-scan
Jul 22, 2026
Merged

mountiny merged 7 commits into
Expensify:mainfrom
callstack-internal:perf/share-short-mentions-scan

Conversation

@adhorodyski

@adhorodyski adhorodyski commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

useShortMentionsList scans the whole personal details collection (about 50k entries on large accounts) to build the list of usernames on the current user's private email domain. The hook mounts once per composer input and once per short mention in every visible message. Each instance ran its own scan, and every personal details write (avatar, presence, display name) re-ran all of them.

This PR moves the scan into one shared cached function, so all instances reuse a single result per personal details update. The scan itself is now a single loop instead of a map plus filter pass, and it drops a redundant public-domain check per entry (once the current user's domain is known to be private, a matching domain must be private too).

The hook reads the data through useOnyx with a selector, which compares the small output list by value. Components re-render only when the username list really changes, for example when someone joins the domain. The current user's email comes from a useOnyx(ONYXKEYS.SESSION) selector, so the list also recomputes when the signed-in user changes. A unit test covers that switch.

Consumers (RNMarkdownTextInput, ShortMentionRenderer) are unchanged and the hook returns the same shape.

Follow-up to #96500 (same issue) but independent of it: no shared files, branched from main.

Fixed Issues

$ #96612
PROPOSAL:

Tests

  1. Sign in with an account on a private email domain that has coworkers on the same domain (for example you@company.com and coworker@company.com).
  2. Open a report and type @coworker (without the domain) in the composer. Verify it is highlighted as a mention while typing.
  3. Send a message containing @coworker. Verify the rendered message styles it as a user mention, and @yourshortname is styled as a self-mention.
  4. Send @nosuchuser. Verify it renders as plain text.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests. Mention highlighting is computed from locally cached personal details and works offline.

QA Steps

Same as Tests.

  • 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

adhorodyski and others added 2 commits July 21, 2026 12:24
Every mounted useShortMentionsList instance scanned the entire personal
details collection and re-ran it on every personal details write. The
scan now lives in a module-level memoized function shared by all
instances, subscribed via a useOnyx selector so consumers only
re-render when the username list content actually changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@adhorodyski adhorodyski changed the title Share the short mentions scan across useShortMentionsList instances perf: share scans across useShortMentionsList instances Jul 21, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/hooks/useShortMentionsList.ts 100.00% <100.00%> (+8.69%) ⬆️
... and 35 files with indirect coverage changes

adhorodyski and others added 2 commits July 21, 2026 15:22
…licit

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@adhorodyski
adhorodyski marked this pull request as ready for review July 21, 2026 14:04
@adhorodyski
adhorodyski requested review from a team as code owners July 21, 2026 14:04
@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and ZhenjaHorbach and removed request for a team July 21, 2026 14:04
@melvin-bot

melvin-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

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

@melvin-bot
melvin-bot Bot requested review from a team and mountiny and removed request for a team July 21, 2026 14:05
@melvin-bot

melvin-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

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

@adhorodyski

Copy link
Copy Markdown
Contributor Author

#96500 needs to go first

Comment thread src/hooks/useShortMentionsList.ts Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a5b25984b0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useShortMentionsList.ts Outdated
adhorodyski and others added 2 commits July 22, 2026 13:19
The domain-wide mention list must not shrink to the people appearing in
search results when the hook renders inside SearchScopeProvider.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@adhorodyski

Copy link
Copy Markdown
Contributor Author

Addressed AI feedbacks.

@ZhenjaHorbach

ZhenjaHorbach commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

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 proper code patterns were followed (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 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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.
  • 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
2026-07-22.15.49.28.mov
Android: mWeb Chrome
2026-07-22.15.49.28.mov
iOS: HybridApp
2026-07-22.15.49.28.mov
iOS: mWeb Safari
2026-07-22.15.49.28.mov
MacOS: Chrome / Safari
2026-07-22.15.44.41.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

LGTM!

@mountiny
mountiny merged commit 3bcf18d into Expensify:main Jul 22, 2026
33 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR and no help site documentation updates are required.

Why: This is a pure performance refactor of the internal useShortMentionsList hook. It moves the personal-details scan into a single shared, memoized function so all hook instances reuse one result per Onyx write, replacing a per-instance map+filter with a single loop. The PR explicitly notes that consumers (RNMarkdownTextInput, ShortMentionRenderer) are unchanged and the hook returns the same shape.

There is no change to any user-facing behavior, feature name, UI label, tab, setting, or flow — short mentions (typing @username without the domain) already work and continue to work identically. Nothing under App/docs/articles describes this hook or documents behavior that this change alters, so there is nothing to add or update.

No draft PR was created.

@adhorodyski, if you believe any user-facing behavior changed that should be documented, let me know and I'll create the help site PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.43-1 🚀

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

Bundle Size Analysis (Sentry):

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.

5 participants