Debugging the Angular JS Routing Lifecycle

18 October 2014

On the first day at my new job at Tailster, I threw myself at diagnosing an Angular JS bug, despite my general lack of knowledge and experience in Angular. Long story short, if you ever need to trace what route and what controllers are being called, you can add the following code to your your rootscope function:

$rootScope.$on('$stateChangeStart',function(event, toState, toParams, fromState, fromParams){
  console.log('$stateChangeStart to ''- fired when the transition begins. toState,toParams : \n',toState, toParams);
$rootScope.$on('$stateChangeError',function(event, toState, toParams, fromState, fromParams){
  console.log('$stateChangeError - fired when an error occurs during transition.');
$rootScope.$on('$stateChangeSuccess',function(event, toState, toParams, fromState, fromParams){
  console.log('$stateChangeSuccess to ''- fired once the state transition is complete.');
// $rootScope.$on('$viewContentLoading',function(event, viewConfig){
//   // runs on individual scopes, so putting it in "run" doesn't work.
//   console.log('$viewContentLoading - view begins loading - dom not rendered',viewConfig);
// });
  console.log('$viewContentLoaded - fired after dom rendered',event);
$rootScope.$on('$stateNotFound',function(event, unfoundState, fromState, fromParams){
  console.log('$stateNotFound ''  - fired when a state cannot be found by its name.');
  console.log(unfoundState, fromState, fromParams);

Here's the StackOverflow question that helped me trace and fix the issue.

Tags: AngularJS, debugging, Javascript

Add a Comment

1 Comment