redhat-developer / redhat-developer/lsp4ij
Inconsistent diagnostics behaviour due to range
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
-
If a language server specifies
1<<32 - 1(4294967295) fordiagnostic.range.end.characterthen it does not appear to work. I guess JetBrains still does not support this per this other claim from 2019. I understand that no consensus has been reached there but could this "known issue" be documented somewhere in this repository? -
If my diagnostics array has a) one valid diagnostic with a "non-crazy" range and b) a second diagnostic with said crazy range, neither of them will show up and I do not see a
Received notification 'textDocument/publishDiagnostics'message in the "Traces" section. Why would the traces be filtered out? 🤔
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 reproducing the two diagnostic cases described in the issue: a range ending at 4294967295 and an array combining valid and extreme ranges. Inspect the diagnostic publishing and trace behavior to identify whether the notification is filtered. Done means the behavior is explained and the unsupported range or trace limitation is documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100