Tracking dependencies of Signal
s
#543
Labels
A-reactivity
Area: reactivity and state handling
C-enhancement
Category: new feature or improvement to existing feature
Feature request
In not-so-small apps, it is easy to lose sight of the effects an event can have. In particular, all the signals that are tracking a given signal. I would like to know if there is a way to obtain a "dependency tree" for a given
Signal
showing all signals that are tracking a givenSignal
and how its changes are tracked. I was thinking of a tree of dependencies. Then, the order of execution would be given in the order of the tree.Current solution
One thing I can think of is to attach an effect to every
Signal
in your app and log a message upon change. Then, changing aSignal
would trigger all its listeners to log a message. This retrieves all dependent nodes, but not the order of execution as a tree, just a possible trace.Use cases
Things I would do with such a dependency tree:
Signal
's change takes too long, I would like to disable only the affected UI. This would also signal "we are working on your request" in all the relevant parts of the UI for the particular firing event.The text was updated successfully, but these errors were encountered: