Stackless Conductor

Hi,

I'm wondering why you have effectively enforced a stack architecture for Conductor? I know you've done this for handling the back button and history, but I have an app which has just a series of tabs which the user can switch between (this is a custom tab setup - not an Android TabLayout as seen in the Conductor Demo). So, there is no need for the back button and view history.

I've got around the problem by getting the stack from the Router, reordering it, and putting it back. But surely there is a nicer solution?

Start by reading the Router implementation and its stack, back-button, and history handling; the issue does not name specific files or tests. Compare that behavior with the custom tab use case and determine the intended API for navigation without stack ordering. Done means the use case no longer requires manually retrieving and reordering the Router stack.

Written by the indexing model from the issue text.