Currently, the NavigationPath is a list of IdentifiedScreens. However, we will need to store more information in NavigationPathElements in the future to enable Tabbed screens and overlays. Also, paths need to be 'split-able' into multiple levels, allowing path elements to contain paths
Solution
Introduce the Either type NavigationPathElement that exposes a common interface that all navigation path elements need to implement. This PR does not contain any work towards tabbed path builders but is only preparing the transition.
In preparation of #19.
Problem
Currently, the NavigationPath is a list of IdentifiedScreens. However, we will need to store more information in NavigationPathElements in the future to enable Tabbed screens and overlays. Also, paths need to be 'split-able' into multiple levels, allowing path elements to contain paths
Solution
Introduce the Either type NavigationPathElement that exposes a common interface that all navigation path elements need to implement. This PR does not contain any work towards tabbed path builders but is only preparing the transition.