eclipse-xtext / eclipse-xtext/xtext
provide custom IBreakpointImportParticipant for xbase languages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
we dont provide a custom IBreakpointImportParticipant which leads to DefaultImportParticipant being used and thus org.eclipse.xtext.debug.IStratumBreakpointSupport.isValidLineForBreakPoint(XtextResource, int) beeing bypassed
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
Start by tracing how breakpoint imports select between IBreakpointImportParticipant and DefaultImportParticipant for Xbase languages. Read the referenced org.eclipse.xtext.debug.IStratumBreakpointSupport.isValidLineForBreakPoint(XtextResource, int) contract and identify the existing breakpoint import entry points. Done means Xbase breakpoint imports use a custom participant and the valid-line check is no longer bypassed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100