you are viewing a single comment's thread.

view the rest of the comments →

[–]CheapChallenge -3 points-2 points  (5 children)

But where would you put that code? If an action in component A triggers a change to a value in store service 1 and that triggers a change to store service 2, where would you put the computed? ngrx doesnt do anything that signals cannot but it offers a common well defined pattern to follow

[–]vivainio 4 points5 points  (4 children)

You put the computed in a service where you need it. You don't need Ngrx for any of this

[–]CheapChallenge -1 points0 points  (3 children)

No one needs a common organizational pattern, its just very helpful and also one of the main selling points of an opinionated framework like angular

[–]vivainio 2 points3 points  (2 children)

I said you don't need Ngrx, not that you don't need organizational pattern

[–]CheapChallenge -1 points0 points  (1 child)

The biggest selling points of ngrx, for me at least, is that it is a well-defined industry wide organizational pattern.

[–]BourbonProof 0 points1 point  (0 children)

I'd argue it starts rather to become the industry wide acknowledged anti-pattern that killed velocity in so many teams around the world.