eclipse-xtext / eclipse-xtext/xtext
The source mapping between the Xtend and the generated Java files are messed up
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
I have experienced broken source mappings mainly in the LS related source when I was using xtext-core in Eclipse.
I am using org.eclipse.xtext.ide_2.14.0.v20180424-1540.jar.
Opening a type opens up the generated files instead of the Xtend file. It is not true for all types, but for a few. For instance, TopologicalSorter and Document are broken, but it is OK when opening the DocumentExtensions or ServerModule.
Furthermore, the Eclipse debugger stops and opens the generated source instead of the Xtend one. Sometimes the lines are messed up in the Xtend files.
I am happy to give additional input and/or verify something if it helps to resolve this issue. Thanks!
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
Reproduce the issue in Eclipse with org.eclipse.xtext.ide_2.14.0.v20180424-1540.jar, focusing on TopologicalSorter and Document and comparing them with DocumentExtensions and ServerModule. Verify that opening types and debugger stops resolve to the Xtend sources with correct line mappings; the issue is done when the affected mappings no longer open generated Java files or show misaligned lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100