microsoft / microsoft/vscode-java-debug
Support method and field access breakpoints via source editor and Outline view
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
JDI supports Constructor, Methods entry and exit (normal return or exceptional return) and Field (access and modification) breakpoints. Support these via:
- the source editor
- decompiled .class source editor
However, the best place to support this is via the Outline view. This is because the Outline view shows the structure of the .class files (even if the de-compilation was not possible) as well, not only .java files. Also outline view can support direct and easy setting of these breakpoints.
I am aware of FQCN#method mechanism for adding method breakpoints buy it is not clear how to set this for overloaded methods.
Also CTOR and method breakpoints are useful when the source line numbers do not match the actual compiled class bytecode exactly but is in the neoghborhood.
Contributor guide
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
Review how the source editor, decompiled .class source editor, and Outline view currently expose Java elements and breakpoints. Define support for JDI constructor, method entry/exit, and field access/modification breakpoints, including overloaded methods, with the Outline view covering classes whose decompilation fails; verify the behavior in each requested view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100