Repository navigation
[Due for payment 2026-04-23] Migrate SearchAutocompleteList.tsx from useOptionsList to useFilteredOptions #82187
Description
Problem
SearchAutocompleteList.tsx currently uses the useOptionsList hook from OptionListContextProvider, which causes unnecessary background recalculations on every personal details or reports change.
This is part of a larger effort to remove OptionListContextProvider entirely. See parent issue #82193 for full context.
Solution
Replace useOptionsList with useFilteredOptions following the pattern established in PR #74071 (NewChatPage migration).
Current usage:
- Properties used:
options,areOptionsInitialized - Called with: no arguments (defaults to
shouldInitialize: true) - File:
src/components/Search/SearchAutocompleteList.tsx
How options are used:
optionsis passed intogetSearchOptions()to buildsearchOptionsin a useMemooptionsis passed intogetSearchOptions()again for autocomplete participants and IN filter inautocompleteSuggestionsuseMemoareOptionsInitializedcontrols early return insearchOptionsuseMemo (falls back todefaultListOptionswhen false)areOptionsInitializedconditionally renders the mainSelectionList
Migration steps:
- Replace
import {useOptionsList} from '@components/OptionListContextProvider'withimport useFilteredOptions from '@hooks/useFilteredOptions' - Replace
useOptionsList()call withuseFilteredOptions({ enabled: true }) - Replace
areOptionsInitializedwith!isLoading(oroptions !== null) - Update the
searchOptionsuseMemo guard to checkoptions !== nullinstead ofareOptionsInitialized - Update the
autocompleteSuggestionsuseMemo similarly - Update the conditional render for
SelectionList
Complexity: Medium -- multiple usages of options across different code paths
Reference PR: #74071
Tests
- Verify search autocomplete works correctly when typing in the search bar
- Verify autocomplete suggestions appear for participants, chats, and IN filters
- Verify fallback to
defaultListOptionsworks when options are loading - Verify no errors appear in the JS console
- Test on all platforms (iOS, Android, Web, Desktop)
Activity
melvin-bot commentedon Feb 19, 2026
@hoangzinh, @mountiny, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mountiny commentedon Feb 20, 2026
In the backlog
melvin-bot commentedon Mar 5, 2026
@hoangzinh, @mountiny, @shubham1206agra 12 days overdue now... This issue's end is nigh!
mountiny commentedon Mar 5, 2026
@shubham1206agra @hungvu193 How is this one looking?
hoangzinh commentedon Mar 6, 2026
@mountiny same here
10 remaining items
mountiny commentedon Mar 18, 2026
same
hoangzinh commentedon Mar 18, 2026
I'm going to pick this issue next
refactor(search): migrate SearchAutocompleteList to useFilteredOptions
refactor(search): pass searchTerm and betas to useFilteredOptions
[-]Migrate SearchAutocompleteList.tsx from useOptionsList to useFilteredOptions[/-][+][Due for payment 2026-04-23] Migrate SearchAutocompleteList.tsx from useOptionsList to useFilteredOptions[/+]melvin-bot commentedon Apr 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.59-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-04-23. 🎊
For reference, here are some details about the assignees on this issue: