Is there any interest in adding sequential routing as a feature? I.e. most states can be entered at random, but in some cases like long running forms, the UI state tree looks like this:
ParentState
Step1
Step2
Step3
For any parentState marked as a sequential section, UI-Router would support next and back methods such that the Step components would never need to know what the next step or previous step's UI state name.
The best argument I can think of against this feature is that it feels like an extension of ui-router. So if there is a way/plugin architecture for extending ui-router let me know and I will look into it.
This is a (check one box):
Feature Request
Is there any interest in adding sequential routing as a feature? I.e. most states can be entered at random, but in some cases like long running forms, the UI state tree looks like this:
For any parentState marked as a sequential section, UI-Router would support next and back methods such that the Step components would never need to know what the next step or previous step's UI state name.
The best argument I can think of against this feature is that it feels like an extension of ui-router. So if there is a way/plugin architecture for extending ui-router let me know and I will look into it.