What’s the best practice for data/state services on page changes if I need to reset state? Should I provide them via component providers, or reset state on destroy/init and keep them providedIn: 'root'?
We have justfuckinguse CSS, HTTP, React, Rails, Laravel, Docker, AI, Tailwind…
So of course I added Angular 😄
It’s very raw — blame lightly.
https://t.co/WgNo5uubKK
My goal is to keep dumb components really dumb, and only inject in smart/feature components.
But sometimes smart components become too smart, or there are too many inputs.
Any guideline to decide when to inject and when to pass?
I have a question about Angular best practices.
Imagine a UserService that exposes an isLogged signal.
This value is needed in many nested components on the same page.
@katsuba_igor I would say that second is from the Angie GPT. Despite plain variables - first solutions looks better for me. ChangeDetection:0 looks odd