groovy / groovy/groovy-eclipse
Enhance the Variables view for Closure literals
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Recently added Lambda support for Debugger Variables view: https://www.eclipse.org/eclipse/news/4.12/jdt.php#lambda-variables-variable-view
Can a similar enhancement be made for breaking within closure literal blocks?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Eclipse Lambda support documentation and compare its Variables view behavior with debugging inside Groovy closure literal blocks. Trace how the Variables view handles those breakpoints; done means closure-local variables are presented similarly when execution stops within a closure literal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100