Restructure state and flow management #3
Description
Currently the app flow is mainly defined in the router file and is based on beforeResolve actions. This leads to a confusing state management, where its not clear which information can be used as perquisite. Furthermore, the logic of one process step is split between store, router and components which is hard to read for anyone interested in the demo as reference implementation.
To solve this issue, I propose to define which information needs to be available on each view and move the logic to establish this to the views themself. It should be possible to get the information needed to root to the previous step by the data available on the current step.
This issue is resolved if there is no state manipulating logic left in the router and each process step is clearly defined in a view.