On tasks, I added a getter that when clicked, will hit a debugger the next time that function is executed or queued.
Considerations
stopAfterTaskCount might be nice to reset every "tick". This way, even in normal development, we'd catch some stack overflows and be able to report. People could set that number to Infinity in production.
For #24
This isn't ready yet. It needs review and some documentation.
This adds 3 things:
stopAfterTaskCount
Allows you to specify how many total tasks should be allowed to run. For example:
This is useful for debugging because it will prevent stack overflows.
breakOnTaskName
Allows you to break on a particular task:
"click on this to break" getter
On tasks, I added a getter that when clicked, will hit a debugger the next time that function is executed or queued.
Considerations
stopAfterTaskCount might be nice to reset every "tick". This way, even in normal development, we'd catch some stack overflows and be able to report. People could set that number to Infinity in production.
breakOnTaskName has to be passed the exact name.