Quick architecture check: when do you actually use effect()? ðŸ§
Best practice tip: reserve effect() for external side effects like logging, analytics, or DOM manipulation - never for state synchronization that computed() can handle cleanly.
Best practice tip: reserve effect() for external side effects like logging, analytics, or DOM manipulation - never for state synchronization that computed() can handle cleanly.
Oct 13, 2026 · 4:00 PM UTC
3
14
131
16,458
@angular I definitely break this rule when we use components as entry points and pass feature flags down through input signals, effects then forwarding them to services. I got inspired by toObservable()
Let me know if there's a better solution
github.com/angular/angula…
Let me know if there's a better solution
github.com/angular/angula…
1
0
1
430
@angular We use effect heavily to replace the business logic codes we used to write in a rxjs subscriptions.
0
0
0
46