Reputation: 3573
$scope.$apply
will no longer be part of Angular 2. Then how do we let Angular know to update the DOM if any of the bound properties have been changed outside the regular angular execution context?
Taken from a blog post by Minko Gechev:
No more $scope.$apply
But how then AngularJS knows that anything outside it’s execution context has taken a place? Lets think where the changes might come from:
- setTimeout
- setInterval
- prompt (yeah, there are people who still use it…)
- XMLHttpRequest
WebSockets
…
For which the answer is:
I understand that patching the browser built-in javascript functions to notify of any changes to Angular is something that can be done in a relatively safe manner (without introducing subtle bugs) and would be very convenient for the developer. But what about third party APIs (such as jQuery.fadeIn
) or if the browser exposes some new asynchronous API which isn't covered? What's the substitute for old $scope.$apply
?
Upvotes: 22
Views: 13040
Reputation: 16373
NgZone
from coreprivate zone: NgZone
in your constructorthis.zone.run(() => {});
where you would normally scope.$apply
or
ChangeDetectorRef
private chRef: ChangeDetectorRef
chRef.detectChanges();
Upvotes: 26
Reputation: 13479
So the library that does all this monkey patching is zone.js.
jQuery.fadeIn
calls setInterval
, setInterval
is monkey patched, as long as you called jQuery.fadeIn
within a zone.run
.
zone.fork
and zone.run
kind of replace $scope.$apply
, but it's different because it detects itself when asynchronous things have finished, whereas you have to call $scope.$apply
manually when you know things have finished.
See also this question+answer: Use zone.js to detect current execution context from anywhere?
if the browser exposes some new asynchronous API which isn't covered?
I guess they will patch that too.
If everything else fails, you can still call zone.afterTask()
manually.
I guess that's what you were looking for :)
Upvotes: 15