EDIT: Here is an even easier solution, tested and working nicely:
In my main controller I simply have
$scope.$on('$stateChangeStart', function(event, toState, toParams, fromState, fromParams) {
if (toState.resolve) {
$scope.showSpinner();
}
});
$scope.$on('$stateChangeSuccess', function(event, toState, toParams, fromState, fromParams) {
if (toState.resolve) {
$scope.hideSpinner();
}
});
This shows the spinner whenever we are about to go to a state that has anything to resolve and hides it, when the state change is complete. You might want to add some check up the state hierarchy (i.e. also show the spinner if a parent state that is being loaded resolves something) but this solution works fine for me.
Here is my old suggestion for reference and as an alternative:
In your application controller, listen to the stateChangeStart
event and check if you are about to switch to a state where you want to show a spinner during resolve (see https://github.com/angular-ui/ui-router/wiki/Quick-Reference#wiki-events-1)
$rootScope.$on('$stateChangeStart', function(event, toState, toParams, fromState, fromParams){
if (toState.name == 'state.with.resolve') {
$scope.showSpinner(); //this is a function you created to show the loading animation
}
})
When you controller finally gets called, you can hide the spinner
.controller('StateWithResolveCtrl', function($scope) {
$scope.hideSpinner();
})
You also might want to check for any errors that may have occurred during resolve by listening to the $stateChangeError
event and hiding the animation while you handle the error.
This is not totally clean as you distribute the logic for the spinner between controllers, but it's a way. Hope it helps.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…