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
[Due for payment 2026-07-01] [No QA] perf: Search S4 useSearchSnapshot data layer #93940
The Search screen was running parallel data pipelines across variants (notably the flat-expense path), duplicating the two-phase optimistic-row merge and the getSections projection. That double-pipeline meant redundant heavy work on every render and blocked the broader Search decomposition effort tracked in #92079.
Solution
Introduced useSearchSnapshot, a single data layer hook that <Search> consumes for every variant and feeds into the existing SearchList. The hook owns the full projection (both getSections stages, group sub-snapshots, sort, columns, defer gating, highlight stamping) and absorbs the two-phase optimistic-row resilience, so the screen runs the live merge and optimistic lifecycle exactly once. This is a behavior-preserving hydrated facade — identities-only projection is deferred to S5/S6.
changed the title [-][No QA] perf: Search S4 useSearchSnapshot data layer[/-][+][Due for payment 2026-07-01] [No QA] perf: Search S4 useSearchSnapshot data layer[/+]on Jun 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.18-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
[-][No QA] perf: Search S4 useSearchSnapshot data layer[/-][+][Due for payment 2026-07-01] [No QA] perf: Search S4 useSearchSnapshot data layer[/+]melvin-bot commentedon Jun 24, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.18-2 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-07-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 29, 2026
@FitseTLT Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Jun 30, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jun 30, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Jul 2, 2026
Payment Summary
Contributor+: @FitseTLT due $250 via NewDot
flaviadefaria commentedon Jul 31, 2026
Approved: @FitseTLT due $250 via NewDot