Thanks Mr. Sander. I have done away with Inheritance.
Partha Majumdar http://www.partha.majumdar.org On Sat, Sep 29, 2018 at 9:24 AM Sander Elias <[email protected]> wrote: > Hi Partha, > > You should try to stay away from inheritance as a paradigm. While it > works, it has a tendency to create hard to maintain apps. The paradigm is > too easy to abuse, and add extra "levels" in the inheritance chain. This > makes really hard to debug issues. (I could make a snarky remark here, > about that you just have proven this ;) ) > There is a reason the gang of 4 stated: "prefer composability over > inheritance". > > In Angular, we have services we can inject, and use to store > business logic, and/or often used code. You can even use services that just > accumulate certain other services. And you can use services to hold > factories. > This makes it easier to maintain and test your app. > > With kind regards > Sander > > -- > You received this message because you are subscribed to the Google Groups > "Angular and AngularJS discussion" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
