You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor: split SearchContext into narrow Query, Results, and Selection providers #91423
The monolithic SearchContext combined query state, results/data, and selection state in a single context object. Any component that consumed even one field would re-render whenever any of those three axes changed, causing unnecessary re-renders across Search and related UI.
Solution
Split SearchContext into three narrow providers: SearchQueryProvider (query string and filter state), SearchResultsProvider (results data, loading, and sort config), and SearchSelectionProvider (selection set and bulk-action state). Migrated 90+ consumers to the matching narrow hooks (useSearchQuery, useSearchResults, useSearchSelection), removed the old shim and re-exports, and added SearchContextDefinitions.ts for shared types to avoid circular imports. The public Search component API is unchanged.
Activity
Pujan92 commentedon Jun 2, 2026
Looks like automation failed here, this is due for payment. @mountiny
Pujan92 commentedon Jun 3, 2026
No checklist is needed, as it was a refactor task
melvin-bot commentedon Jun 3, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Jun 4, 2026
Payment Summary
Contributor+: @Pujan92 due $250 via NewDot
twisterdotcom commentedon Jun 5, 2026
$250 approved for @Pujan92 in Report ID: R00AmBWWwmKw.
Zapier Logs
Run ID: 00040eee-f02e-a27e-8602-65bee048df44SO: https://stackoverflowteams.com/c/expensify/questions/7582