Problem
Search list rendering still relied on a legacy SearchList component with a getListItem factory and shared renderItem, even after dedicated views were introduced for most search types. Invoice and trip transaction types still routed through this monolithic shell instead of the dedicated expense views, leaving duplicate prop bundles and unused legacy code.
Solution
This PR finalizes the Search router by routing invoice and trip through existing ExpenseFlatSearchView and ExpenseGroupedSearchView, extracting shared props into commonViewProps, moving isTransactionMatchWithGroupItem to SearchUIUtils, and deleting the unused SearchList component, getListItem factory, and shared renderItem. <Search> is now a pure router over five dedicated views with preserved behavior for every search type.
PR
#95370
Issue Owner
Current Issue Owner: @daledah
Problem
Search list rendering still relied on a legacy
SearchListcomponent with agetListItemfactory and sharedrenderItem, even after dedicated views were introduced for most search types. Invoice and trip transaction types still routed through this monolithic shell instead of the dedicated expense views, leaving duplicate prop bundles and unused legacy code.Solution
This PR finalizes the Search router by routing invoice and trip through existing
ExpenseFlatSearchViewandExpenseGroupedSearchView, extracting shared props intocommonViewProps, movingisTransactionMatchWithGroupItemtoSearchUIUtils, and deleting the unusedSearchListcomponent,getListItemfactory, and sharedrenderItem.<Search>is now a pure router over five dedicated views with preserved behavior for every search type.PR
#95370
Issue Owner
Current Issue Owner: @daledah