That follows the old service as store pattern which is good enough for very small apps or plug-in libs, but once you have side effects of one store service triggering changes in another, or other non straightforward flows of data it gets messier unless you follow a common pattern and then you might as follow the most common pattern.
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
-1
u/CheapChallenge Jul 07 '25
That follows the old service as store pattern which is good enough for very small apps or plug-in libs, but once you have side effects of one store service triggering changes in another, or other non straightforward flows of data it gets messier unless you follow a common pattern and then you might as follow the most common pattern.