angular.js/docs/content/error/resource/badname.ngdoc

@ngdoc error
@name $resource:badname
@fullName Cannot use hasOwnProperty as a parameter name
@description

Occurs when you try to use the name `hasOwnProperty` as a name of a parameter.
Generally, a name cannot be `hasOwnProperty` because it is used, internally, on a object
and allowing such a name would break lookups on this object.
fix(*): protect calls to hasOwnProperty in public API 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-10-05 09:49:09 +00:00			`@ngdoc error`
			`@name $resource:badname`
			`@fullName Cannot use hasOwnProperty as a parameter name`
			`@description`

			Occurs when you try to use the name `hasOwnProperty` as a name of a parameter.
			Generally, a name cannot be `hasOwnProperty` because it is used, internally, on a object
			`and allowing such a name would break lookups on this object.`