You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will have to be handled with care because angular-data does not wrap items in custom classes or depend on the use of getters and setters. Computed properties will have to be updated during dirty checking loops. Angular-data runs its own dirty checking loop whenever a digest loop is triggered on the $rootScope. However, a digest loop triggered only on some child $scope won't trigger angular-data's dirty check. This could result in unexpected behavior as the computed property could be out of date. Of course, the developer can manually trigger angular-data's digest loop with DS.digest(), but I'd like to avoid developers' code being smattered with DS.digest calls.
No description provided.
The text was updated successfully, but these errors were encountered: