Disclaimer This question doesn't regard the patter of creating components and their subcomponents (as discussed here). It doesn't consider the choice of components and their type (as discussed here). It's not meant to be opinion based and I do apologize in advance if my linguistic skills fail me when formulating it.
We have a component with quite some logic (specific to that certain component and none other). The logic updates a lot of entries based on input in others. The updates are governed by a complex set of irregular business rules. With time, the component grew large and needs some heavy scrolling. That suggests that it's time to refactor it.
In C#, I could use partial and create a file holding the rest of the class out of sight for the current development. As far I've looked, it's been asked for but isn't implemented at the moment, nor about to.
I could create a set of separate utility classes specific for this particular component. It seems like a hack, though. I'm figuring like so.
<plopp (click)="onClick($event)">...
...
onClick(event: KeyboardEvent) { Aux.onClick(event, this.something, ...); }
Also, Even if I created a separate class handling all the events (it would make huge sense in our case), I still need a method that the template file can bind to (and then convey the call to the auxiliary) and it'd require to send most of the properties to the the auxiliary too.
What is the by-the-book approach in this case? As the linkage shows, I've dug into that extensively but I come up with rather little. Admittedly, it's not the most common scenario but it is a scenario and I prefer to believe that it can be addressed in a proper way.