From the feedback of Vassil after one of the trainings:
"We need to revisit what is stored in the state of each "page" and when is this state reset. For example, users do a search, then click to calendar, go to a specific month, then day view of one day, then select one of the reports. They read the report, then go back to read another one of that day, but they have to re-navigate again. I suggest to go over the UI and define for each page which state properties are reset and how depending on navigation path. Might be a good opportunity now that we have hooks."
We need to define this per component, not per page.
Should we also keep track of the chosen vizualization type for the ReportCollection?
Maybe also the selected Mosaic layout?
From the feedback of Vassil after one of the trainings: "We need to revisit what is stored in the state of each "page" and when is this state reset. For example, users do a search, then click to calendar, go to a specific month, then day view of one day, then select one of the reports. They read the report, then go back to read another one of that day, but they have to re-navigate again. I suggest to go over the UI and define for each page which state properties are reset and how depending on navigation path. Might be a good opportunity now that we have hooks."