Closed jeme closed 10 years ago
@numair that is not really the plan for transitions, transitions are meant to provide a means to do different things depending on source and destination state. So we can get closer to a state machine.
Loading screens are quite a different thing, and I am not really sure how to solve that problem along side with the introduction of ng-animate.
That said, i will keep the thought in mind for transitions...
@jeme aha! So you're purely affecting state, and leaving view-level transitions for somewhere else. I guess it's a bit confusing with all of the conflicting terminology for things (i.e., ui-router is as much about non-ui state as it is about visual ui state). Thanks for the clarification.
@numair There is now very basic (minimalistic) support for including loaders for views, it requires you to use resolve on states. See https://github.com/dotJEM/angular-routing/issues/63
It's still very basic... But should make it easier to display loaders.
Closing as It don't quite seem to make all that much sense. Can always reopen or create a new issue.
Hi -- I'm assuming the point of the stateTransitions is to allow for some sort of "loading..." screen, etc before the next state-view is loaded? This seems to be the issue with using ui-router out of the box.