Doing a POST on a Restangular.all() about restangular HOT 8 CLOSED

You're right, there's no way to post on "root" element. This needs to be added.

However, doing Restangular.all("accounts") doesn't really fetch anything, it just creates Restangular object, so, the implementation would be something like this:

Restangular.all("accounts").getList().then(function(accounts) {
  accounts.post({... data ...});
});

from restangular.

Actually, I'm thinking in implementing both:

// Option 1 on Root Restangular Obj
Restangular.all("accounts").post({data});

//Option 2 for every Restangular collection
Restangular.all("accounts").getList().then(function(accounts) {
  accounts.post({... data ...});
});

from restangular.

Oopsy, forgot the "getList()" in my sample, corrected.

+1 for the 1st option since you might probably want to directly do a POST to the collection without fetching it with a GET. Also supporting the 2nd option would be quite nice.

from restangular.

I'll implement both :). I'll try to do this tomorrow.

Thanks for the input man!

from restangular.

Also uncommented test, and added another one. Tests passing.

from restangular.

Nice. I've taken a quick look at your code and here is some feedback. Should we limit this approach to only a few HTTP methods? Or should we support them all? It's not that impossible that a user might want to perform a DELETE on a collection in order to remove all elements. Or use PUT instead of POST to create new elements (not really good IMO but that's its problem).

In fact, even the GET can be done (I'm talking about the one returning an object and not an array). In particular for people having a wrapper around their collections and wanting to retrieve this wrapper and not the real data (because in that case, they could use the extractor you already coded).

With no restriction, you will have no unhappy users ;-)

Also, I will improve tests when all work will be merged and Lodash available.

from restangular.

Hey,

I actually think that this methods as "default" wrappers are ok.

I'm planning to add a "customOPERATION" method on both collections and elements like:

account.customPOST(path, params, headers) where path can be either null or a value, so that you could do POST /accounts/messages

Same for elements, so that users can have the flexibility to do whatever they want, besides the "defaults" from Angular.

from restangular.

It'd be implementing: #19

from restangular.