Skip to content

Chore: Migrate SearchAutocompleteList to the new SelectionListWithSections#81293

Merged
mountiny merged 42 commits intoExpensify:mainfrom
software-mansion-labs:chore/migrate-search-autocomplete-list
Feb 13, 2026
Merged

Chore: Migrate SearchAutocompleteList to the new SelectionListWithSections#81293
mountiny merged 42 commits intoExpensify:mainfrom
software-mansion-labs:chore/migrate-search-autocomplete-list

Conversation

@staszekscp
Copy link
Copy Markdown
Contributor

@staszekscp staszekscp commented Feb 3, 2026

Explanation of Change

The PR migrates SearchAutocompleteList to use the newly refactored SelectionListWithSections in order to improve performance and finish the migration.

image

Fixed Issues

$ #65658
$ #79353
PROPOSAL: N/A

Tests

  1. Open the SearchRouter by clicking on the magnifying glass icon or by pressing Cmd+K
  2. Start typing someone's name
  3. When the name is written, the list should highlight the first matching option
  4. Press enter and see if you get navigated correctly (web only, on mobile just open the report)

Offline tests

QA Steps

  1. Open the SearchRouter by clicking on the magnifying glass icon or by pressing Cmd+K
  2. Start typing someone's name
  3. When the name is written, the list should highlight the first matching option
  4. Press enter and see if you get navigated correctly (web only, on mobile just open the report)

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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 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.
  • 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.
  • 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
Screen.Recording.2026-02-05.at.12.26.47.mov
Android: mWeb Chrome
iOS: Native
Screen.Recording.2026-02-05.at.11.19.13.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-02-05.at.16.13.50.mov

@staszekscp staszekscp changed the title Chore/migrate search autocomplete list Chore: Migrate SearchAutocompleteList to the new SelectionListWithSections Feb 3, 2026
@staszekscp staszekscp marked this pull request as ready for review February 3, 2026 12:05
@staszekscp staszekscp requested review from a team as code owners February 3, 2026 12:05
@melvin-bot melvin-bot bot requested review from aimane-chnaif and trjExpensify and removed request for a team February 3, 2026 12:05
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Feb 3, 2026

@aimane-chnaif 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]

@staszekscp staszekscp marked this pull request as draft February 3, 2026 12:05
Copy link
Copy Markdown

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

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

ℹ️ 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".

@aimane-chnaif
Copy link
Copy Markdown
Contributor

@codex review

Copy link
Copy Markdown

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

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: 1dfba52e38

ℹ️ 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 on lines +259 to +261
// Note: We can't easily subscribe to focus/blur events on the ref, so we update on query changes
// which happen when the user types (meaning input is focused)
}, [textInputRef, autocompleteQueryValue]);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Synchronize external input focus on blur/focus events

This effect only updates updateExternalTextInputFocus when autocompleteQueryValue changes, so focus transitions that do not change text are missed. In flows like opening search and navigating immediately with arrow keys (or refocusing without typing), isTextInputFocusedRef can become stale in BaseSelectionListWithSections, which allows shouldSyncFocus to move focus to list rows and unexpectedly blur the text input.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is a comment that have appeared twice already. After a lot of testing and playing with the arrows the text input stays focused correctly

Comment on lines +776 to +777
const debounceHandleSearch = useDebounce(() => {
const actionId = `debounce_search_${Date.now()}_${Math.random().toString(36).substring(2, 9)}`;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Memoize the debounced search callback

useDebounce cancels and recreates its timer whenever the callback identity changes, and this inline function is recreated on every render. That means unrelated rerenders during the debounce window can drop a pending handleSearch call, causing intermittent missing autocomplete requests even when the query has not changed.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This will be memoized by the React Compiler

@aimane-chnaif
Copy link
Copy Markdown
Contributor

I feel typing input is not quite smooth compared to staging.

i.e. Try type expense, command+A and delete to clear search
Especially input is not immediately cleared after backspace.

Screen.Recording.2026-02-12.at.8.36.15.pm.mov

@staszekscp
Copy link
Copy Markdown
Contributor Author

Hey! I've noticed that you've been comparing dev.new.expensify.com to staging.new.expensify.com - the problem you're seeing is probably related to the fact that you're using a dev server, not an optimised and production-ready build. When checking the ad-hoc build for the PR everything seems to work way smoothly

Copy link
Copy Markdown
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

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

Let's give it a go but still be on a look out for any regressions QA team might catch.

@melvin-bot melvin-bot bot requested a review from mountiny February 13, 2026 07:43
Copy link
Copy Markdown

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

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: 1dfba52e38

ℹ️ 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".

@mountiny
Copy link
Copy Markdown
Contributor

@staszekscp conflicts and codex comment

@staszekscp
Copy link
Copy Markdown
Contributor Author

Just a moment and will be ready!

Copy link
Copy Markdown

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

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: 1dfba52e38

ℹ️ 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".

@staszekscp
Copy link
Copy Markdown
Contributor Author

If the tests pass, we're good to go!

@mountiny mountiny merged commit 94e72fc into Expensify:main Feb 13, 2026
31 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

✋ 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
Copy link
Copy Markdown
Contributor

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

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.19-5 🚀

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

@aimane-chnaif
Copy link
Copy Markdown
Contributor

No regressions found in staging QA. Good job 🎉

@mountiny
Copy link
Copy Markdown
Contributor

Nice one

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.

7 participants