Replies: 1 comment 1 reply
-
@robvaneck, you misunderstand Signals. They are not made for managing multiple events. What you want, is to use the If you could give me a prototype on Stackblitz, I can give you a jump start. You also want to listen to this: https://youtu.be/205cMTcQ82Y?si=0wfpTP706ECdGUIo |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Which @ngrx/* package(s) are relevant/related to the feature request?
effects, signals
Information
I want scoped effects...
so that
effect()
isnt called everytime when one of the signals change that are used inside the componentComing from rxjs: signals are unlogical, unflexible, and fire everytime. I get that they wanted to get rid of zone.js... but how do you perform actions/subscriptions/tap/side effects TO the signal store... when some signal changes? It's not very nice design IMO that Angular gave us.
What I currently do (bad design, infinite loop)
What I need is this:
Describe any alternatives/workarounds you're currently using
...
I would be willing to submit a PR to fix this issue
Beta Was this translation helpful? Give feedback.
All reactions