Problem
Task search results still render through the legacy SearchList shell, which mixes routing, layout, and type-specific rendering in one component. That makes the task view harder to maintain and prevents the search refactor from giving each search type its own dedicated view with stable, focused responsibilities.
Solution
Add a dedicated TaskSearchView that composes the shared useSearchListViewState hook and SearchListViewLayout over BaseSearchList, matching the pattern used by ExpenseFlatSearchView. The router now dispatches the task type to this view, which renders TaskListItem rows with no column data, no exit animation, and suppressed long press. The parent-report name still comes from the report-attributes selector inside TaskListItem, so behavior stays unchanged.
PR
#94820
Issue Owner
Current Issue Owner: @mallenexpensify
Problem
Task search results still render through the legacy
SearchListshell, which mixes routing, layout, and type-specific rendering in one component. That makes the task view harder to maintain and prevents the search refactor from giving each search type its own dedicated view with stable, focused responsibilities.Solution
Add a dedicated
TaskSearchViewthat composes the shareduseSearchListViewStatehook andSearchListViewLayoutoverBaseSearchList, matching the pattern used byExpenseFlatSearchView. The router now dispatches the task type to this view, which rendersTaskListItemrows with no column data, no exit animation, and suppressed long press. The parent-report name still comes from the report-attributes selector insideTaskListItem, so behavior stays unchanged.PR
#94820
Issue Owner
Current Issue Owner: @mallenexpensify