How to debug signal setter? #165
Replies: 3 comments 1 reply
-
Second that. To share an experience, a signal that was setup with equality that always trigger started to behave in a loop because I add somewhere |
Beta Was this translation helpful? Give feedback.
-
Would it help to print the current stack trace with signals observer for setting? https://api.flutter.dev/flutter/dart-core/StackTrace/current.html |
Beta Was this translation helpful? Give feedback.
-
Do you remember my old PR which put the signal debugLabel to be more present and easy to declare? What we have here is in the same category than A stack trace would have at least gave some hints for where to search. Would it be possible to have smth like
VSCode extension is already doing a lot in there, I should use it more often :) |
Beta Was this translation helpful? Give feedback.
-
I'd like to understand the path that leads to setting a value of a signal.
Let's assume I have drift_example app and I would like to backtrack what part of the code has set the
activeCategory
signal. During the runtime of the app there might be several places where the signal value is accessed and assigned (e.g. onTap callbacks etc.). I would like to be able to determine which callback changed the value by setting a breakpoint and observing the stacktrace.Is that possible?
Beta Was this translation helpful? Give feedback.
All reactions