angular.js/test/ngResource, branch v1.2.10

fix($resource): prevent URL template from collapsing into an empty string

2014-01-03T07:07:27+00:00

if url template would result in an empty string, we should make a request
to '/' instead.

Closes #5455
Closes #5493

fix($resource): Always return a resource instance when calling class methods on resources.

2013-11-21T17:51:02+00:00

Previously, calling `MyResource.save(myResourceInstance)`returned
a promise, in contrast to the docs for `$resource`. However,
calling `MyResource.save({name: 'Tobias"})`already correctly
returned a resource instance.

Fixes #4545.
Closes #5061.

fix($resource): don't use $parse for @dotted.member

2013-11-12T00:17:34+00:00

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.

fix(*): protect calls to hasOwnProperty in public API

2013-10-07T16:01:13+00:00

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

fix(ngResource): Remove request body from $delete

2013-10-04T23:50:08+00:00

Prevent the  obj.$delete instance method from sending the resource as the request body.  This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body.

Closes #4280

fix($resource): pass transformed value to both callbacks and promises

2013-10-03T00:03:53+00:00

Closes #3817

test: rename / remove duplicate unit tests

2013-08-23T19:43:42+00:00

feat(minerr): log minerr doc url in development

2013-08-15T20:23:18+00:00

Closes #3566

style(minerr): prefer component name as namespace

2013-08-09T21:12:04+00:00

Closes #3527

fix(resource): check whether response matches action.isArray

2013-07-31T20:17:37+00:00

When using $resource you must setup your actions carefully based on what the server returns.
If the server responds to a request with an array then you must configure the action with
`isArray:true` and vice versa.  The built-in `get` action defaults to `isArray:false` and the
`query` action defaults to `isArray:true`, which is must be changed if the server does not do this.
Before the error message was an exception inside angular.copy, which didn't explain what the
real problem was. Rather than changing the way that angular.copy works, this change ensures that
a better error message is provided to the programmer if they do not set up their resource actions
correctly.

Closes #2255, #1044