Future Guidance

[subodh-malgonde]

@christopherthielen Great work on this project! I stumbled across this project after going through the discussion on #894 on angular-ui-router. Not to see these features get integrated with the main project was quite disappointing :(

I noticed that you are now the main developer/maintainer on angular-ui-router along with being the main developer on this project. So is this project going to be integrated with angular-ui-router? If yes, can we have a tentative target (3 months/ 1 year?) The angular-ui-router github page mentions that their API is likely to change in the near future. Is this true with this project as well?

It would be really nice to have a note on these lines on the main page.

[christopherthielen]

I am not the only maintainer of UI-Router. Edit: Also, I make no promises about the accuracy of the comments below.

Short-term:

• UI-Router overhaul/redesign: @nateabele and I have been redesigning the core of UI-Router to allow more flexibility during transitions. We should have a preview "real soon now".
• The overhaul will greatly simplify coding of things like "deep state redirect" and "default substate of abstract states". At that time, a separate library for DSR will become unnecessary.

Mid-term:

• Something like Future States will make it into core UI-Router. It won't be future states, but it may be influenced by it.

Long-term:

• Something like Sticky States (parallel activated states) may make it into core, but it definitely won't be what you know as "Sticky States" today. Sticky states is a kludgey implementation of a narrow (but popular) use case. We'd like to take what I learned from Sticky States and come up with a more general solution before integrating this sort of feature in core.