AngularJS ui-router 1.0+ uses $transition events instead of the old $stateChangeSuccess, etc.
Modified the code to use these events / objects instead. Haven't completely tested all of gsapify-ui-router functionality, but have managed to fix some glaring bugs presented by the change in ui-router.
My main reason for doing this, was leave: blocks on the states in ui-router 1.0+ would not be used. Therefore, I could not properly animate a leaving view. Because of this, my exiting view on every transition would just simply disappear, resulting in a blank page with the new view coming in.
This patch fixes basic compatibility for ui-router 1.0+, properly using the animations provided by the leave: blocks for states, allowing for animation of exiting views again, as originally intended.
AngularJS ui-router 1.0+ uses $transition events instead of the old $stateChangeSuccess, etc.
Modified the code to use these events / objects instead. Haven't completely tested all of gsapify-ui-router functionality, but have managed to fix some glaring bugs presented by the change in ui-router.
My main reason for doing this, was
leave:
blocks on the states in ui-router 1.0+ would not be used. Therefore, I could not properly animate a leaving view. Because of this, my exiting view on every transition would just simply disappear, resulting in a blank page with the new view coming in.This patch fixes basic compatibility for ui-router 1.0+, properly using the animations provided by the
leave:
blocks for states, allowing for animation of exiting views again, as originally intended.