fix($parse): handle interceptors with undefined expressions

When calling `$parse` with `undefined` as the expression and with an interceptor, then when the function is evaluated, then call the interceptor Closes: #13367 Closes: #13373
angular · Nov 25, 2015 · 7bb2414 · 7bb2414
1 parent da11c1b
commit 7bb2414
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 1 deletion.
diff --git a/src/ng/parse.js b/src/ng/parse.js
@@ -1775,7 +1775,7 @@ function $ParseProvider() {
           return addInterceptor(exp, interceptorFn);
 
         default:
-          return noop;
+          return addInterceptor(noop, interceptorFn);
       }
     };
 

diff --git a/test/ng/parseSpec.js b/test/ng/parseSpec.js
@@ -3165,6 +3165,17 @@ describe('parser', function() {
           expect(called).toBe(true);
         }));
 
+        it('should invoke interceptors when the expression is `undefined`', inject(function($parse) {
+          var called = false;
+          function interceptor(v) {
+            called = true;
+            return v;
+          }
+          scope.$watch($parse(undefined, interceptor));
+          scope.$digest();
+          expect(called).toBe(true);
+        }));
+
         it('should treat filters with constant input as constants', inject(function($parse) {
           var filterCalls = 0;
           $filterProvider.register('foo', valueFn(function(input) {