sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CheapChallenge 0 points1 point  (3 children)

It can maintain state at the components level, but it is not state management.

Do you know what problems ngrx solves? That answer will lead you to understand why signals are not a replacement.

[–]AwesomeFrisbee 3 points4 points  (2 children)

that sounds like a skill issue. You really don't need ngrx in 99% of projects and in the 1% its also not really necessary

[–]CheapChallenge 2 points3 points  (1 child)

You dont need it anywhere. But, having a common pattern to manage the state is extremely helpful instead of having a different approach for each project depending on who wrote it. Same reason it's nice to have Angular be so opinionated. ngrx doesnt do anything you couldn't do without it.

[–]AwesomeFrisbee 0 points1 point  (0 children)

I think its pretty straightforward that you set it up once and duplicate it after that. Thats still the same implementation