Nested resources that can also be top level resources

[TheLudd]

Hello.
I have a restful backend that contains companies and each company has a list of services. I get a companies list of services at the URL "company/{companyId}/servicelist"
However each service is also considered a "top level" entity. To update a service I need to send a PUT request to the address "service/{serviceId}".

If i retreive the list of services for a company with Restangular, each one of the retreived services will have an "incorrect" route. Like this:

Restangular.one("company", 42).all("servicelist").getList().then(function(serviceList) {
    var firstService = serviceList[0]; // firstService.id is 1.
    firstService.name = "A new name";
    firstService.put(); // will post to company/42/servicelist/1
});

Can I configure this so that the PUT request will be sent to "service/1"?

[mgonto]

Hey,

Thanks for using the library.

The idea is to use Nested resources for putting and posting, but you can use Restangular anyway for your case.

You should do something like this:

var firstService = serviceList[0]

var firstService = Restangular.restangularizeElement(null, firstService, 'service');

firstService.put()

Using restangularizeElement, you can restangularize any element you want, even an already Restangularized element :).

Let me know if this works out for you!

[TheLudd]

Looks promising but when I use the the code you provided, the service still has the parentResource "company" after calling restangularizeElement with null as the first argument. Is this correct?

[mgonto]

You're absolutely righ!

Try again with version 1.0.3. I fixed that bug