|
STSMACOM-251
Closed
puts us on a path to being able to do this in SearchAndSort modules. 3 Sprints for potential variance to get all modules doing this. I'm not sure we can do it all within SearchAndSort, so a first step would be a spike to have all SandS modules do this with a centralized change. This is easy to do at the module level if routing has been refactored (similar to ui-users) - that work can be broken out and distributed. If the solution cannot be completely centralized, the bulk of the module-level work for dev teams would be splitting any resources that the search view (Search and filter pane, results list) uses apart from the resources used by the detail view and using the API introduced in
STSMACOM-251
Closed
to handle the navigation appropriately. This would mean a single sprint (possibly less) work at the module level.
|