angular.js/test/ngResource, branch v1.1.3 fix($http): do not encode special characters `@$:,` in params 2013-02-14T22:52:46+00:00 Vojta Jina 2013-02-14T22:39:55+00:00 288b69a314e9bd14458b6647532eb62aad5c5cdf encodeURIComponent is too aggressive and doesn't follow http://www.ietf.org/rfc/rfc3986.txt with regards to the character set (pchar) allowed in path segments so we need this test to make sure that we don't over-encode the params and break stuff like buzz api which uses @self. This is has already been fixed in `$resource`. This commit fixes it in a same way for `$http` as well. BREAKING CHANGE: $http does follow RFC3986 and does not encode special characters like `$@,:` in params. If your application needs to encode these characters, encode them manually, before sending the request. 
encodeURIComponent is too aggressive and doesn't follow http://www.ietf.org/rfc/rfc3986.txt
with regards to the character set (pchar) allowed in path segments so we need
this test to make sure that we don't over-encode the params and break stuff
like buzz api which uses @self.

This is has already been fixed in `$resource`. This commit fixes it in a same way
for `$http` as well.

BREAKING CHANGE: $http does follow RFC3986 and does not encode special characters
like `$@,:` in params. If your application needs to encode these characters, encode
them manually, before sending the request.
fix($resource): params should expand array values properly 2013-02-14T22:52:46+00:00 Mark Nadig 2013-01-30T15:41:39+00:00 2a2123441c2b749b8f316a24c3ca3f77a9132a01 Today, calling e.g. var R = $resource('/Path/:a'); R.get({a: 'foo', bar: ['baz1', 'baz2']}); results in a query string like "/Path/doh?bar=baz1,baz2" which is undesirable. This commit enhances resource to use $http to encode any non-url parameters resulting in a query string like "/Path/doh?bar=baz1&bar=baz2". BREAKING CHANGE: if the server relied on the buggy behavior then either the backend should be fixed or a simple serialization of the array should be done on the client before calling the resource service. 
Today, calling e.g. var R = $resource('/Path/:a'); R.get({a: 'foo', bar: ['baz1', 'baz2']}); results in a query
string like "/Path/doh?bar=baz1,baz2" which is undesirable. This commit enhances resource to use
$http to encode any non-url parameters resulting in a query string like "/Path/doh?bar=baz1&bar=baz2".

BREAKING CHANGE: if the server relied on the buggy behavior then either the
backend should be fixed or a simple serialization of the array should be done
on the client before calling the resource service.
fix(resource): Update RegExp to allow urlParams with out leading slash 2013-02-14T22:43:55+00:00 Fredrik Bonander 2013-01-23T09:53:49+00:00 b7e1fb0515798e1b4f3f2426f6b050951bee2617 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. 
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.
feat($resource): expose promise based api via $then and $resolved 2013-02-12T06:24:21+00:00 Igor Minar 2013-02-12T05:43:30+00:00 dba6bc73e802fdae685a9f351d3e23c7efa8568a Expose $then and $resolved properties on resource action return values which allow checking if a promise has been resolved already as well as registering listeners at any time of the resource object life-cycle. This commit replaces unreleased commit f3bff27460afb3be208a05959d5b84233d34b7eb which exposed unintuitive $q api instead and didn't expose important stuff like http headers. 
Expose $then and $resolved properties on resource action return values which
allow checking if a promise has been resolved already as well as registering
listeners at any time of the resource object life-cycle.

This commit replaces unreleased commit f3bff27460afb3be208a05959d5b84233d34b7eb
which exposed unintuitive $q api instead and didn't expose important stuff
like http headers.
feat(resource): add $q/$resorved property to Resource 2013-01-24T04:57:26+00:00 Partap Davis 2013-01-17T22:21:35+00:00 f3bff27460afb3be208a05959d5b84233d34b7eb 






revert: fix($resource): Route constructor, updated RegExp
2013-01-23T00:32:02+00:00

Igor Minar

2013-01-23T00:30:35+00:00

ffe5e01584ec1c10930a9a01ce4cec2ec888966b

This reverts commit 06ed8ef0127bf80610eba17b5021d1f483d0b0bf.

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





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

Fredrik Bonander

2012-09-21T11:39:45+00:00

06ed8ef0127bf80610eba17b5021d1f483d0b0bf

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.




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

pavelgj

2013-01-08T22:19:40+00:00

b2f46251aca76c8568ee7d4bab54edbc9d7a186a

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'.




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

Misko Hevery

2013-01-18T06:01:50+00:00

af89daf4641f57b92be6c1f3635f5a3237f20c71

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





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

Sudhir Jonathan

2012-11-27T06:24:35+00:00

8991680d8ab632dda60cd70c780868c803c74509

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

Closes #1403





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

Closes #1403