You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a User, I'd like to have native support for angular-ui-router#1.x so that I don't have to use workarounds that mimic angular-ui-router#0.x's deprecated behavior.
Cause
With ui-router 1.x the emission of $stateChangeXXX events were removed, for state load it now uses the method onEnter from the $transitionProvider on the config phase (or onEnter on state configuration).
AC
User should be able to use angular-css while using angular-ui-router#1.x without need for manual workaround.
Note
The workaround below could be used in the config phase of your module, although it's not the most desirable solution.
As a User, I'd like to have native support for
angular-ui-router#1.x
so that I don't have to use workarounds that mimicangular-ui-router#0.x
's deprecated behavior.Cause
$stateChangeXXX
events were removed, for state load it now uses the methodonEnter
from the$transitionProvider
on the config phase (oronEnter
on state configuration).AC
angular-css
while usingangular-ui-router#1.x
without need for manual workaround.Note
config
phase of your module, although it's not the most desirable solution.The text was updated successfully, but these errors were encountered: