Handling $resource object parameter

Question

Having the following $resource service:

myService.factory('Phones', function ($resource) {
    return $resource('/api/Phones', { phoneName: '@phoneName' }, {
        submit: { method: 'POST', },
    });
});

Calling submit on the returned $resource object will post the phoneName as a parameter e.g. /api/Phones?phoneName=Nokia. However calling the same resource object with the GET method will also use the phoneName parameter as undefined e.g. /api/Phones?phoneName=undefined.

Is it possible to prevent the phoneName to appear for the GET method using the same $resource object?

Thanks!

Roy Daniels · Accepted Answer · 2013-04-12 05:09:33Z

1

Try changing your service to this:

myService.factory('Phones', function ($resource) {
    return $resource('/api/Phones', {}, {
        submit: { 
          method: 'POST'
        }
    });
});

That way you only define the paramater 'phoneName' on the 'submit' action and not all actions.

Edit: You don't need to define phoneName as a param in the $resource action.

edited Apr 12, 2013 at 5:09

answered Apr 3, 2013 at 2:44

Roy Daniels

6,3092 gold badges29 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

doorman Over a year ago

Thanks for your answer. Now if I call the service like this: Phones.submit({ phoneName: 'Nokia' }); it will no longer replace the @phoneName attribute instead it outputs: /api/Phones?phoneName=@phoneName Any idea how to solve this?

Collectives™ on Stack Overflow

Handling $resource object parameter

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related