Add possibility to override URL in custom $resource actions

[guillaume86]

This change adds the possibility to overridde the template URL when creating $resource custom actions:

var Person = $resource('/Person/:id', {}, {
  clear: { method: 'POST', url: 'Person/clear' }
});

Person.clear(); // POST /Person/clear

[BrynCooke]

I would really like to see this happen as it is impossible to work with some rest services at the moment without creating several resources.

I note that the pull request conflicts with master now, I have fixed it on my branch, shall I submit another pull request?

[nolazybits]

Same here... It's nice to have the resource with one URI and default CRUD but if you want to push it a little further it gets annoying. Would love to have this functionality also...
Any idea when this will be merged in the main repo?
Cheers

[nolazybits]

@BrynCooke I'm trying to use your fork and I have a question. Does the binding between the url parameters and the object properties work?
ie if I have

return $resource( '', {},
{
get: { method:'GET', isArray: true, url:'user/:userId'},
}

and I call it like myResource.get({userId:1}), looking at charles I see the request being
/user/:userId?userId=1

Cheers,
Xavier

[nolazybits]

@BrynCooke
Ok just forked angularjs branch and added this feature (heavily inspired by the mods you had done in your fork)
https://github.com/zeflasher/angular.js

Cheers

[nolazybits]

Kindof hijacking the discussion here but done a PR (#2054) to address the above issue (heavily base on @BrynCooke code).
Cheers

[IgorMinar]

@zeflasher I guess you meant @guillaume86's code ;-)

I'm going to close this PR as #2054 is more generic and handles this use case as well. Thanks @guillaume86 for your contribution!

[nolazybits]

Ooops, my bad... Indeed Guillaume86's code...

[guillaume86]

No problem

[elaleprieto]

¡this is great!

¡must be in the next release!

👍

:)

[FlyersWeb]

Hi,
I'm using v1.0.2 from Google CDN. I wanted to know if this feature is integrated in this version or not ?
Thanks.

[worldspawn]

It'd be sweet(er) if we could prefix the url with a magic token that prepends the resource base url to the new url so it doesn't need to be typed out over and over. So

var Person = $resource('/Person/:id', {}, {
  clear: { method: 'POST', url: 'Person/clear' }
});

might become

var Person = $resource('/Person/:id', {}, {
  clear: { method: 'POST', url: '@/clear' }
});

Not sure if it matters that :id would be prepended. I think as long as there was no id provided to the call it will be stripped from the url.