Add support for range diagnostics under cursor #1586
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@prabirshrestha Merry Christmas! 🎄 Thanks, and hope you’re having a great holiday season! |
|
@satorunooshie can you provide the steps to use. i don't see much difference. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for range-based diagnostics, aligning with the Language Server Protocol (LSP) Specification.
Previously, diagnostics were matched only to specific start positions, limiting usability for multi-line or range diagnostics.
This update ensures vim-lsp provides functionality consistent with VSCode, which already supports range-based diagnostics.
The highlighted codes represents the area where textDocument/codeAction can be triggered.
Below is the corresponding diff for the changes.
Before
After
VSCode behavior