-
Notifications
You must be signed in to change notification settings - Fork 27.4k
docs(error/$rootScope/inprog): improve understanding and diagnosis of the error #7719
Conversation
Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.
If you need to make changes to your pull request, you can update the commit with Thanks again for your help! |
You can see the new error doc page in action here: http://ci.angularjs.org/job/angular.js-pete/570/artifact/build/docs/error/$rootScope/inprog |
); | ||
``` | ||
|
||
It is not possible to tell which from the stack trace, but we happen know in this case that it is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"to know"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Magic thanks
}); | ||
}); | ||
} | ||
``` | ||
|
||
The controller constructor is always instantiated from within an $apply cycle, so if the third-party component called our callback synchronously, we'd be trying to enter the $apply again. | ||
We expect that our callback will be call asynchronously, and so from outside Angular. Therefore, we |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: 'will be called'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
Closed by 4124a65 |
This change improves the documentation related to "$digest/$apply already in progress" errors.
It describes common scenarios where this error occurs and shows a demonstration of debugging a situation where the error has occurred, including a runnable example.
See #5549