[Due for payment 2026-06-30] [Payment due @ZhenjaHorbach] [No QA] Avoid building archived reports ID set in Search getSections pipeline

[mountiny]

Problem

The Search getSections pipeline (Search/index.tsx and useSearchSections.ts) used useArchivedReportsIDSet(), which subscribed to the entire REPORT_NAME_VALUE_PAIRS collection and rebuilt a Set via an O(n) Object.entries scan on every collection change — for every search type. This was wasteful because getSections only needs a single report's archived status, and only for task searches.

Solution

Removed useArchivedReportsIDSet() from the Search pipeline. Components now pass the raw reportNameValuePairs collection into getSections/getTaskSections, which calls isArchivedReport(reportNameValuePairs?.[key]) directly (O(1) lookup) where needed. Same data source and coverage as before; the eager Set construction is eliminated.

PR

#94182

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.17-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [Payment due @ZhenjaHorbach] [No QA] Avoid building archived reports ID set in Search getSections pipeline #94182

If no regressions arise, payment will be issued on 2026-06-30. 🎊

For reference, here are some details about the assignees on this issue:

• @TMisiukiewicz does not require payment (Contractor)

[melvin-bot]

@TMisiukiewicz Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Awaiting Payment)