redhat-developer / redhat-developer/lsp4ij
Show LSP diagnostic errors in `Project Errors`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
Some language servers (ex: our Qute language servers) can report errors for closed document. It would be nice if we could see those erros in the project errors:
vcode provides this feature and can show all errors in the error view and for Qute for instance you can see all errors of all Qute templates (closed and opened):
@ia3andy is it a feature that you would like to have?
I think this feature should be customized per language server definition and we should provide an API to know if LSP diagnostics must be displayed in Project Errors or not.
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 the existing LSP diagnostic handling and the Project Errors integration. Identify where language-server definitions can expose the proposed setting, then verify that diagnostics for closed documents appear in Project Errors; the issue names no files or tests, so those must be located first.
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
- Needs clarification
- Newbie friendliness
- 35/100