Computed properties

[jmdobry]

[jmdobry]

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.

[jmdobry]

Turns out, angular-data's hook into the $rootScope's digest cycle seems pretty reliable. I don't think there will be a problem here.