Unable to create a non static action using GET about angular-resource-sails HOT 10 CLOSED

I think you could handle this case like this:

var User = sailsResource('user',
    { notifications: { method: 'GET', isArray: true, url: '/user/:id/notifications' }}
};
var userNotifications = User.notifications({id: userId});

from angular-resource-sails.

This is exactly my second example except I explicitly say where does userId comes from. It works great this way but I thought It would be great to pass the User object which contains the userId instead of the userId. Don't you think ?

from angular-resource-sails.

Could you do me.$notifications() (from your example)?

from angular-resource-sails.

no because notification is a GET request and according to the code (see the link in my first message) the method should be added to the resource and not to the instances of that resource.

from angular-resource-sails.

Ah, I see. So yeah you can either do two calls or you could modify sailsResource to attach all of the GET calls onto the instance. I believe ngResource supports the latter so we have precedence to do that.

from angular-resource-sails.

so get request would be attached to both right ?

from angular-resource-sails.

After reviewing $resource's docs it says

HTTP GET "class" actions: Resource.action([parameters], [success], [error])
non-GET "class" actions: Resource.action([parameters], postData, [success], [error])
non-GET instance actions: instance.$action([parameters], [success], [error])

So I guess GETs don't get added to the instance. How you do what you need to do with ngResource?

from angular-resource-sails.

You are right I never worked with $resource but I just found it convenient to do this this way because sails allow get requests on models. But I completely understand you if you want to follow the original $resource behavior

from angular-resource-sails.

We could certainly support it, but I'd like to follow Angular's $resource example where possible.

from angular-resource-sails.

As I said I understand your point. That's why I closed the issue

from angular-resource-sails.