Inheritance about angular-styleguide HOT 5 CLOSED

My $0.02. The rule of thumb in Object Orientation ( dating to the 1980s) is "favor composition over inheritance". That advice tilts toward injected services for common functionality, perhaps with a light weight prototype to do some internal service orchestration.

Deep inheritance chains are a code smell, whether in static or dynamic languages, class or prototypal inheritance.

from angular-styleguide.

If the code is reusable, shouldn't that code be in a service of its own?

from angular-styleguide.

For services I guess you're right but for controllers? Or if I feel a controller should be inherited, I'm doing something wrong?

from angular-styleguide.

It's not wrong or right, it's more about what you are trying to accomplish and finding the right tool for that. So let's take as step back and think about what prototypal inheritance is good for. Often it helps when you have lots of instances of the same object and you want to share the functions. If you create 1000 customer objects and they all share some functions such as checkCredit, it would be nice not to use memory for 1000 functions. All 1000 object instances could share that checkCredit function. But are you going to create lots of controllers where this would be super helpful? Where is it valuable? 5, 10, 100?

But you might have code that every controller seems to have, that's when I drop that code into a service/factory. Could I use prototypal inheritance? Sure, but factories are just as good and simple to test.

I'm not trying to way you either way, just give you some food for thought. So go with your instincts on this.

from angular-styleguide.

@johnpapa - What do you think for this article: Object-oriented AngularJS Services ?

This article follow the guide suggestions ?

from angular-styleguide.