customGETLIST doesn't use setParentless correctly

[Meekohi]

It seems like setParentless should not change urls when dealing with collections, only single objects. Not sure if this is a documentation or code bug, but doesn't behave how I would expect:

Restangular.setParentless(['events']);
Restangular.one("calendars",1).all("events").customGETLIST("search",options);
// should make a request to //calendars/1/events/search
// since it is a collection and not an individual object,
// but makes it to //events/search instead

[Meekohi]

Note that this works:

Restangular.setParentless(['events']);
return Restangular.one("calendars",1).getList("events/search",options);

but you get "events/search" search objects instead of "events".

[pedromarce]

Hi @Meekohi, you are right, is the problem related to the use of customGETLIST or would the request also be wrong if you just ask for the events?

Restangular.one("calendars",1).all("events") // Calls //calendars/1/events or //events??

Thanks

[mcacek]

In my experience, the following is true.

Restangular.setParentless(['events'])
Restangular.one("calendars",1).all("events")

Results in a request to /events whereas I would have expected a request to /calendars/1/events

[pedromarce]

Thanks @mcacek, I agree, I have labeled as a bug, we'll try to get it fixed, but any PR would be much appreciated :)

[mcacek]

I'll see what I can do in regards to a PR.

[Meekohi]

Alas, this issue was big enough to bounce me back to ngResource. At a high level I think there is a big conflict in Restangular between the nice "auto-magic" routing and the reality of a complicated REST API. Some way to declare up-front what your resources and routes are would be really helpful toward getting clear expected behavior. For completeness, in this case the situation was:

GET /calendars/1/events         #the usual, works correctly
GET /calendars/1/events/search  #same endpoint but with ES backend. Not sure how to do this
PUT /events/1                   #needs setParentless to work correctly