baseAccounts.put(existingAccount) instead of existingAccount.put()

[synergetic]

It seems to me having put(), patch(), and delete() methods on base object just like post() is quite natural. Also, I happen to deal with hierarchical data, and restangularizing account object which has subAccounts array property seems to be a little more work. If there were those methods on base object, I wouldn't need to restangularize them. Am I missing something?

[mgonto]

Hey,

They're not in the collection as PUT, DELETE and PATCH aren't collection methods. They're element methods.

Anyway, you could either add them to every collection or use customPUT, customDELETE and so on.

For example, you could add an element transformer like this:

RestangularProvider.setOnElemRestangularized(function(elem, isCollection) {
  if (isCollection) {
    elem.put = function(obj) {
       return obj.put();
   }
  }
  return elem;
})

And that's it, with that you've added that method to all collections.

[mgonto]

For customPUT, you'd need to do collection.customPUT(elem.id, elem)

[mgonto]

I didn't understand the second problem.

Tell me if this solves this :)

[synergetic]

When I add a new entity, I do the following (and it works):

Restangular.all('account').post($scope.account);

Similarly, why not to have the following:

Restangular.all('account').put($scope.account); 

or maybe

Restangular.one('account', $scope.account.id).put($scope.account); 

That way I wouldn't need my account entity to be restangularized.
As for the second problem (which is related to the above concern), I have the following code:

RestangularProvider.setResponseExtractor(function (response, operation, what, url) {
    var jsonObj;
    if (operation === "getList") {
        jsonObj = response.objects;
        delete response.objects;
        jsonObj.meta = response;
    } else {
        jsonObj = response;
    }
    return jsonObj;
});

However, my account entity has subAccounts property, which is also a collection. Restangular seems to restangularize my account entities, but not its subAccounts property. So I have to do some extra work to restangularize them too. Can you suggest me a proper way of dealing with the issue?

[synergetic]

By the way I don't really understand difference between restangularizeElement and restangularizeCollection. Both have the same arguments:

restangularizeElement(parent, element, route)
restangularizeCollection(parent, element, route)

What does "element" mean in the restangularizeCollection() method? I thought it is a collection, no?

[mgonto]

That way I wouldn't need my account entity to be restangularized.

The idea of put is that you're modifying an element that you've received from the server at some point. If you've received it from the server, it should have already been Restangularized.

Anyway, if you want to do this PUT, you have 2 options:

// Option 1
var restangularObj = Restangular.one('account', id);
_.extend(restangularObj, $scope.account);
restangularObj.put();

// Option 2
// I know this undefined undefined is ugly, I'm pushing a fix for that this week as well, 
// so that for customPUT and customPOST and not safe operations, 
// the element to post is the first thing (instead of params and header)
var accounts = Restangular.all('accounts');
accounts.customPUT($scope.account.id, undefined, undefined, $scope.account);

Both of this will do exactly what you need.

However, my account entity has subAccounts property, which is also a collection. Restangular seems to restangularize my account entities, but not its subAccounts property. So I have to do some extra work to restangularize them too. Can you suggest me a proper way of dealing with the issue?

So, when you receive an account, it has a property subAccounts that are also a list of accounts? And you care about both accounts and subAccounts?

In that case, you can use the methods you mention above. I'm going to change the documentation, but basically, restangularizeCollection receives a collection as an argument as you just said. However, it won't restangularize each element inside, which it should. I'm going to push this tomorrow, but basically, if the URL for this subAccounts is the same you should do the following. However, for now it won't add the functions needed to the elements, but I'll add this as a functionality as it should be done, for now, you'll need to restangularize each element manually as well which I know is a pain. You'll get it fixed tomorrow.

Restangular.restangularizeCollection(account.parentResource, account.subAccounts, account.route);

Hope this works!

[synergetic]

Thank you! I'm new to angularjs thing; Restangular better suits my taste than $resource. Please, keep it going.

[mgonto]

Thanks again for using it :). I'll try to fix this 2 issues you mention.

[tomjakubowski]

Hey, was the issue with restangularizeCollection not restangularizing its component elements resolved? I don't see a commit related to it since this issue was closed.

[mgonto]

Hey,

There wasn't an issue about that here. It does restangularize elements, otherwise when you're getting a list via getList restangular wouldn't work

[tomjakubowski]

hmm… it doesn't seem to be restangularizing elements when I have setFullResponse(true) set. For example this:

  function getList() {
    var topicsEl = FanmobRestangular.all('topics');

    return topicsEl.getList().then(function (res) {
      var topics = res.data.topics;
      return topics;
    });
  }

is not returning an array of restangularized elements (if I try to do something like call .all('subresource') on one of them, I get a "has no method 'all'"). I have to do this ugly workaround before returning the topics:

      // ugly hack to work around mgonto/restangular#224
      _.each(topics, function (el, index) {
        topics[index] = FanmobRestangular.restangularizeElement(topics,
                                                                el,
                                                                el.name);

[mgonto]

Hey,

Can you create a plunkr or jsfiddle with the example so that I can reproduce this?

Thanks!!!

Reopenning

[mgonto]

Any news on the jsfiddle?