LivelyKernel / LivelyKernel/lively.next
Finding the method called from a UI action
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
**What would you like to achieve?**
When I was trying to fix https://github.com/engageLively/galyleo-dashboard/issues/202, I had to figure out what routine was drawing the Halo in response to a ctrl-click. Eventually I figured it out by putting a `debugger;` statement in the `Halo` initializer and tracing the call stack, but there has to be a better way.
Contributor guide
Research direction
Reproduce the ctrl-click action that draws the Halo and start at the Halo initializer, using the debugger and call stack as described. The issue names no target file, test, or concrete replacement for this tracing workflow, so completion would require defining and validating a better way to find the routine invoked by a UI action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100