Is it problematic to use traditional classes and objects in Angular code? For instance, when refactoring to separate specific logic from messy code, I often create a separate file like logic-handler.ts and define a class like so...
export class LogicHandler {
var1: Obj1;
var2: Obj2;
constructor(/* ... */) { /* ... */ }
}
I then instantiate an object of this class within the component.ts file to handle the logic. However, a senior member of my team always expressed reluctance towards this approach as he was unsure of how Angular handles new instances of LogicHandler.
Should we be concerned about this? Is there a valid reason for worry?
I am hoping someone can address my concerns or offer a better solution to this issue. Personally, I find my method simpler and more straightforward for testing purposes.