template type conversion errors are difficult to debug #1974
Description
I have some simple angularJS code like this:
<div ng-controller="todoController">
<span> temp = {{tempVal()}} </span>
</div>the bug is easy enough, tempVal is a string, not a method.
pretend this bug is burried inside a 10,000 line application, what is the most effective way to track down the offending line?
I am using Chrome and have the Batarang extension installed, however all I get is a cryptic stack trace:
TypeError: string is not a function
at http://localhost:6202/lib/angular-1.0.4/angular.js:6213:13
at Object.$interpolate.fn (http://localhost:6202/lib/angular-1.0.4/angular.js:4829:22)
at Object.watchExpression (http://localhost:6202/AddSomeControl/index.html:416:29)
at Object.Scope.$digest (http://localhost:6202/lib/angular-1.0.4/angular.js:7783:38)
at Object.Scope.$apply (http://localhost:6202/lib/angular-1.0.4/angular.js:7991:24)
at Object.$delegate._proto_.$apply (http://localhost:6202/AddSomeControl/index.html:500:30)
at http://localhost:6202/lib/angular-1.0.4/angular.js:932:13
at Object.invoke (http://localhost:6202/lib/angular-1.0.4/angular.js:2813:25)
at bootstrap (http://localhost:6202/lib/angular-1.0.4/angular.js:930:12)
at angularInit (http://localhost:6202/lib/angular-1.0.4/angular.js:906:5) angular.js:5601I'm stuck trying to figure out how, using these tools in a complex application, I could discover that the error is somewhere around that tempVal() line.
i tried setting a break point right when the error is being logged and looked up the callstack, and see a caught exception in $get.Scope.$digest that can maybe tell me the parent scope id (this.target.$id), along with what "watcher" (this.length) it is that crashed, and the previous completed html element (this.value).... is that the best way? what a pain :(
FYI the only line in the stack trace that references my actual document (index.html, line 500), line 500 is past the end of the source document, so it's referencing some angular script injected into the header, thus does not seem to be useful for debugging.