When using onEnter to redirect to a state, if the new state is a child of the current state, an infinite loop occurs.
Example:
$stateProvider
.state 'inventory',
url: '/inventory'
templateUrl: 'views/inventory.html'
controller: 'InventoryCtrl'
onEnter: () ->
$state.go 'inventory.low'
.state 'inventory.low',
url: '/low'
templateUrl: 'views/inventory-table.html'
controller: 'LowInventoryCtrl'
When:
$state.go 'inventory.low'
Is called, the state inventory
is re-initialized, causing it to be called again = infinite loop.
However, if the redirect state is:
$state.go 'otherStateThatIsNotAChild'
This issue does not occur. I assume that the parent state is being re-initialized, but why?
.go
is called on a child state?
1) Why is the parent state being reinitialized when .go is called on a child state?
While a transition is in process, any $state.go/transitionTo will cause the currently in process transition to be Superseded. An in-process transition that is superseded is cancelled immediately. Since your original transition to inventory
is not completed by the time all the states' onEnters are called, the original transition is cancelled and a new transition to inventory.low
is started from the previously active state.
See ui-router src https://github.com/angular-ui/ui-router/blob/master/src/state.js#L897 ...
2) How then, would you handle redirecting to a child state?
You could...
$state.go
in a $timeout()
to allow the original transition to complete before redirecting.In any case, be very sure you want your app to redirect like this. If a user navigated directly to any other child state of inventory (such as inventory.high
), the redirect will still occur, forcing them to inventory.low
which would not be what they intended.
这篇关于Angular JS ui-router如何从父母重定向到子状态?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!