AngularJS: Creating multiple factories for every endpoint?

Question

following some examples, it appears that we can inject a factory which would contain an endpoint for a rest service like so

services.factory('Recipe', ['$resource',
     function($resource) {
        return $resource('/recipes/:id', {id: '@id'});
}]);

This looks great, but imagine I have other endpoints i.e. /users/:id, and /groups/:id, as you can imagine the number of different endpoints are going to increase.

So it is good practice to have a different factory for each endpoint so having ..

services.factory('Recipe', ['$resource',............

services.factory('Users', ['$resource',.............

services.factory('Groups', ['$resource',...............

Or is there another recommended way ?

I really don't see an issue with it but its going to force me to create a lot of factories just for dealing with the different endpoints.

Any help or guidance really apprecaited

Thanks

possible duplicate of Angularjs: a Service that serves multiple $resource urls / data sources? — mpromonet
– mpromonet, Commented Aug 31, 2014 at 8:39

Stewie · Accepted Answer · 2013-12-04 08:52:37Z

99

It's a matter of preference.

But nothing prevents you from consolidating all your resources inside one factory as in:

services.factory('Api', ['$resource',
 function($resource) {
  return {
    Recipe: $resource('/recipes/:id', {id: '@id'}),
    Users:  $resource('/users/:id', {id: '@id'}),
    Group:  $resource('/groups/:id', {id: '@id'})
  };
}]);

function myCtrl($scope, Api){
  $scope.recipe = Api.Recipe.get({id: 1});
  $scope.users = Api.Users.query();
  ...
}

edited Dec 4, 2013 at 8:52

answered Jun 21, 2013 at 11:01

Stewie

60.4k20 gold badges148 silver badges113 bronze badges

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

6 Comments

Martin Over a year ago

Ah! that makes sense, would this method be preferred over the other one? I wouldn't want to be breaking the one responsibility principle, but I think these are the same responsibility ?

Stewie Over a year ago

Yes, I'd prefer this method, because yes, all $resources carry the same responsibility (minus the actual endpoint they are pointing to). If you were using $http to create a more customised models, than separate factories would be a better option.

Eric Novins Over a year ago

This way you only get API instance as well since factories are singletons. I dig it right now, but my API isn't huge yet.

Stephane Over a year ago

@Stewie Cool. But what if you want to have several entries for the Users ? Say, you have some custom method names in the resource definitions. Like, Users: $resource(... confirm: ...) and Users: $resource(... unconfirm: ...). Cheers.

Stephane Over a year ago

@Stewie Maybe something like this ? nodeModule.factory('NodeFirebase', ['$resource', function($resource) { return { Node: $resource( FIREBASE_URL + 'nodes/:nodeId', { nodeId: '@nodeId' }, { add: { method: 'POST', params: {}, isArray: false }, update: { method: 'PUT', params: { nodeId: '@nodeId' }, isArray: false } }), Stuff: $resource( FIREBASE_URL + 'stuff/:stuffId') } } ]);

|

Collectives™ on Stack Overflow

AngularJS: Creating multiple factories for every endpoint?

1 Answer 1

6 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

6 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related