Affects Version/s: None
Fix Version/s: None
Component/s: Dataset Display
Sprint:S04E15 - Kind of Blue, S04E16 - Hard to Earn, S04E17 - Those Who Tell the..., S04E18 - Fiction and Fact, S04E19 - Takk..., S04E20 - Acabou Chorare, S04E21 - 15151, S04E22 - Ceremonials, S04E23 - Mamonas Assassinas, S04E24 - The Piano Guys
To support custom view management, we need a well defined connection between the dataset display frontend internal state and the custom view management operations.
More specifically, we're interested in a subset of the component internal state, which we'll call view state, made up by state items denoting the portion of the dataset display internal state concerning view settings, indeed, custom view management operations can be seen as state items transfer.
Frontend implementation of the dataset display has to generate and consume such state items. The more state items component understands, the richer is the set of elements making up the idea of custom view.
The goal of this task is to implement the State items transfer API, in charge of handling the state items between the frontend component and the custom views/active view settings in response to user actions, as well as initializing the dataset state when served to the front.
- Operations in the api are implemented by the frontend component
- Frontend component is able to produce (getActiveViewSettings()) and interpret (setActiveViewSettings(state)) the following state items (see State Stored by a Custom View for details):
- Visible fields: valid only for the cas of table visualization.
Note: we will support more state items in future epics
Please refer to Component State Management requirements for details.