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

revert: fix($resource): Route constructor, updated RegExp

2013-01-23T00:32:02+00:00

This reverts commit 06ed8ef0127bf80610eba17b5021d1f483d0b0bf.

The reverted commit causes regressions. See comments in the PR:
https://github.com/angular/angular.js/pull/1402#issuecomment-12575399

fix($resource): Route constructor, updated RegExp

2013-01-19T05:28:15+00:00

Update RegExp to allow urlParams with out leading slash (/).
- Will allow reoucese to be loaded from a relative path

Example:
var R = $resource(':path');
R.get({ path : 'data.json' });

Example usage:
Load resources in applications not using webserver, ie local webapp in on a tablet.

fix(ngResource): correct leading slash removal.

2013-01-19T04:52:57+00:00

Fixed an issues with ngResource param substitution where it was incorrectly removing leading slash when param was followed by a non-slash character.
Ex:
'/:foo/:bar.baz/:aux'

params = {
  foo: 'aaa',
  bar: undefined,
  aux: undefined
}

The above params were incorrectly producing '/aaa.baz' but now it results in '/aaa/.baz'.

feat(ngResource): support all $http.config actions

2013-01-18T07:08:39+00:00

This allows the transformation of the $http request in both directions,
headers, caching, and timeout.

fix($resource): HTTP method should be case-insensitive

2012-11-30T21:58:11+00:00

Perform call `angular.uppercase` on all given action methods.

Closes #1403

feat($resource): allow dynamic default parameters

2012-11-28T15:01:57+00:00

Default resource params can now be calculated at runtime if defined
via a function.

fix($resource): prevent default params to be shared between actions

2012-11-24T20:27:24+00:00

Having a $resource defined as:

var R = $resource('/Path', {}, {
  get: {method: 'GET', params: {objId: '1'}},
  perform: {method: 'GET'}
});

was causing both actions to call the same URI (if called in this order):

R.get({}); // => /Path?objId=1
R.perform({}); // => /Path?objId=1

fix($resource): allow falsy values in URL parameters

2012-09-06T23:06:22+00:00

Close #1212

when a param value was 0 (or false) it was ignored and removed from url.
after this fix that only happens if the value is undefined or null.

fix($resource): ignore undefined parameters

2012-09-06T23:06:22+00:00

- $resource should handle multiple params with same name
- ignore slashes of undefined parameters
- fix default parameters issue, mentioned in #875

Closes #875
Closes #782

feat($resource): support custom headers per action

2012-09-06T23:06:21+00:00

Closes #736