fix(#1577) run throttledDigest in a non-reactive manner.

It's possible that a digest loop from one autorun function, triggers another autorun function to be ran. Before this commit, the second autorun thought it was nested in the first autorun. This has as a side effect that when the first autorun re-runs, it will stop the second autorun from running. This commit runs the digest in a non-reactive manner, which means it temporarily resets the current active tracker computation. Therefore no parent-child relation is created between the 2 autorun functions, solving this problem.

Author: sebakerckhof

src/modules/core.js

@@ -131,7 +131,12 @@ angular.module(name, [
         !this.$$phase &&
         !this.$root.$$phase;
 
-      if (isDigestable) this.$digest();
+      if (isDigestable) {
+        // If a digest cycle in one autorun triggers another autorun,
+        // we want to run this second autorun in a non-reactive manner.
+        // thus preventing inner autoruns from being dependent on their parents.
+        Tracker.nonreactive(() => this.$digest());
+      }
     };
 
     // Creates a promise only that the digestion cycle will be called at its fulfillment

tests/client/core.spec.js

@@ -90,6 +90,20 @@ describe('angular-meteor.core', function() {
 
         expect(stop.calledOnce).to.be.true;
       });
+
+      it('should run digest in a non-reactive manner, so autoruns triggered by the digest are not dependent on other autoruns', function() {
+        scope.$watch('foo',function(val) {
+          if (val) {
+            var computation = scope.autorun(angular.noop);
+            expect(computation._parent).to.be.null;
+          }
+        });
+
+        scope.autorun(function() {
+          scope.foo = 'baz';
+        });
+       
+      });
     });
 
     describe('subscribe()', function() {