Yet another conditional
Sure, break down that heavy Angular component into tiny, little, single-function components. What they don’t tell you is that someday soon, you’ll need to prop thread through the layers to be able to craft yet another conditional.
You’ll touch every component, then drone on-and-on during the code review:
“And I did it here, and here.. and here.”
Maybe use a global state
NGRX is going to help, right? Or maybe a shared service with a BehaviorSubject? You’re still touching every single component, and now you have to use a Subscription that will need to be disposed of properly.
Signals / signal store
Signals! Yes, signals will be my savior…
Dammit, Jimmy, we’re stuck on Angular 10 due to some library that can’t be upgraded.