Provide a way to turn off debugging info in production

[IgorMinar]

angular sets ng-binding class and other classes as well as adds $binding object to jqLite/jQuery data storage. This info is not needed in production and is only used by tools like batarang and protractor but are causing performance issues for apps with lots of bindings.

These tools can already intercept the angular bootstrap and change configuration of the app if needed, so they could turn on the debugging info on demand.

I'm thinking that to control the behavior we could use $compileProvider and expose a setter like debugMode() that tools could use.

The debugging info should be off by default in production.

Open questions:

• should we disable this in non-minified angular by default? are the css classes useful for development?

cc: @btford, @rev087, @juliemr

[petebacondarwin]

So my initial thoughts are to move all attaching of ng-binding css classes and $binding data into a function on $compile, say $compile.addBindingClass(element). Then we can swap this for a noop if in production.

[petebacondarwin]

Also I think we should just disable this debugging information for all builds by default. It is trivial to enable if it is needed.

[petebacondarwin]

Obviously we would need to implement updates to Protractor and Batarang to support this

[petebacondarwin]

And also the ngScenario runner would need updating too

[caitp]

the scenario runner is deprecated anyways, so why update it?

[petebacondarwin]

Because although it is deprecated it has not yet been removed and so would suddenly break when upgrading to the new version of AngularJS.

[rev087]

ng-inspector doesn't make use of the ng-binding classes, so this change wouldn't affect it.

Tools could also simply look for the $binding object and friends - clunky, sure, but the clunkiness is contained in tooling and not spilling over to the production lib. So I'd say it's ok to remove them.

Thanks for the heads up by the way!