eclipse-lsp4e / eclipse-lsp4e/lsp4e
[Feature Request]: Please Support Diagnostic.codeDescription to provide external links
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 69
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 6
Description
Hey all,
it would be real nice to be able to navigate from a diagnostic to extended information specified in the CodeDescription field. To achieve this, vscode and Sublime Text just display the Diagnostic.Code field as a link that links to the CodeDescription. Would it be possible to implement this for the problems view and maybe the LSP marker?
This is how it looks in these tools:
Cheers
Bastian
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 locating the Problems view and LSP marker handling that consume diagnostics, then trace how Diagnostic.code and CodeDescription are represented. Done means CodeDescription links can be opened from the diagnostic code in the Problems view and, where supported, the LSP marker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100