eclipse-lsp4e / eclipse-lsp4e/lsp4e
Go to Type Definition contextual menu
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 69
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 6
Description
Today definition and typeDefinition are available with Ctrl+Click but in XML context:
- definition is used to switch from start tag to end tag
- typeDefinition is used to open the grammar bound with XML and select the proper element/attribute declaration in the grammar.
Ctrl+Click on start tag element should just swith to the end tag element and not provide the typeDefinition (which can takes some times).
vscode provides:
- definition with Ctrl+Click
- typeDefinition with a contextual menu

I think LSP4E should provide this menu too.
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 LSP4E's existing definition and typeDefinition handling in the XML context, then inspect how contextual menus are contributed in Eclipse. Done means the XML start-tag Ctrl+Click behavior remains definition-only while typeDefinition is available through a contextual menu, matching the described VS Code behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100