In the foundational epic LPS-130101 the scope of the state items that would be remembered by a custom view was deliberately narrow (see LPS-130174), to the point that only one item was meant to be remembered: the visible columns. In addition to facilitate development, this helps to figure it out the kind of patterns needed to properly implement the state transfer api, without the need of covering all items.
The goal of this epic is to enhance the set of state items remembered by the custom view feature, so that dataset display is improved to handle the following ones:
- Active filters: which is the set of filters and its configurations being used to filter out data items
- Active ordering: which field data is ordered by, and whether it’s ascending or descending.
- Page size: number of items per page.
- Current visualization mode: to which this custom view applies. Most common modes are table, cards, list but there are more.
These state items essentially cover what the user can manipulate via the dataset state manipulation controls (i.e. those not related to custom view management)