angular.js -

Age	Commit message (Collapse)	Author
2014-02-16	chore(errors): rename folders to match namespaces	Peter Bacon Darwin

2014-02-16	docs(bike-shed-migration): fix url-based links refs to AUTO module	Peter Bacon Darwin

2013-11-11	fix($resource): don't use $parse for @dotted.member	Chirayu Krishnappa
	params and paramDefaults support looking up the parameter value from the data object. The syntax for that is `@nested.property.name`. Currently, $resource uses $parse to do this. This is too liberal (you can use values like `@a=b` or `@a \| filter` and have it work - which doesn't really make sense). It also puts up a dependency on $parse which is has restrictions to secure expressions used in templates. The value here, though a string, is specified in Javascript code and shouldn't have those restrictions.
2013-10-07	fix(*): protect calls to hasOwnProperty in public API	Peter Bacon Darwin
	Objects received from outside AngularJS may have had their `hasOwnProperty` method overridden with something else. In cases where we can do this without incurring a performance penalty we call directly on Object.prototype.hasOwnProperty to ensure that we use the correct method. Also, we have some internal hash objects, where the keys for the map are provided from outside AngularJS. In such cases we either prevent `hasOwnProperty` from being used as a key or provide some other way of preventing our objects from having their `hasOwnProperty` overridden. BREAKING CHANGE: Inputs with name equal to "hasOwnProperty" are not allowed inside form or ngForm directives. Before, inputs whose name was "hasOwnProperty" were quietly ignored and not added to the scope. Now a badname exception is thrown. Using "hasOwnProperty" for an input name would be very unusual and bad practice. Either do not include such an input in a `form` or `ngForm` directive or change the name of the input. Closes #3331
2013-08-09	style(minerr): prefer component name as namespace	Ken Sheedlo
	Closes #3527