-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
robustly handle invalid LSP ranges #6512
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -129,7 +129,11 @@ pub mod util { | |
) -> Option<usize> { | ||
let pos_line = pos.line as usize; | ||
if pos_line > doc.len_lines() - 1 { | ||
return None; | ||
// If it extends past the end, truncate it to the end. This is because the | ||
// way the LSP describes the range including the last newline is by | ||
// specifying a line number after what we would call the last line. | ||
log::warn!("LSP position {pos:?} out of range assuming EOF"); | ||
return Some(doc.len_chars()); | ||
} | ||
|
||
// We need to be careful here to fully comply ith the LSP spec. | ||
|
@@ -239,9 +243,20 @@ pub mod util { | |
|
||
pub fn lsp_range_to_range( | ||
doc: &Rope, | ||
range: lsp::Range, | ||
mut range: lsp::Range, | ||
offset_encoding: OffsetEncoding, | ||
) -> Option<Range> { | ||
// This is sort of an edgecase. It's not clear from the spec how to deal with | ||
// ranges where end < start. They don't make much sense but vscode simply caps start to end | ||
// and because it's not specified quite a few LS rely on this as a result (for example the TS server) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (╯°□°)╯︵ ┻━┻ |
||
if range.start > range.end { | ||
log::error!( | ||
"Invalid LSP range start {:?} > end {:?}, using an empty range at the end instead", | ||
range.start, | ||
range.end | ||
); | ||
range.start = range.end; | ||
} | ||
let start = lsp_pos_to_pos(doc, range.start, offset_encoding)?; | ||
let end = lsp_pos_to_pos(doc, range.end, offset_encoding)?; | ||
|
||
|
@@ -947,16 +962,16 @@ mod tests { | |
|
||
test_case!("", (0, 0) => Some(0)); | ||
test_case!("", (0, 1) => Some(0)); | ||
test_case!("", (1, 0) => None); | ||
test_case!("", (1, 0) => Some(0)); | ||
test_case!("\n\n", (0, 0) => Some(0)); | ||
test_case!("\n\n", (1, 0) => Some(1)); | ||
test_case!("\n\n", (1, 1) => Some(1)); | ||
test_case!("\n\n", (2, 0) => Some(2)); | ||
test_case!("\n\n", (3, 0) => None); | ||
test_case!("\n\n", (3, 0) => Some(2)); | ||
test_case!("test\n\n\n\ncase", (4, 3) => Some(11)); | ||
test_case!("test\n\n\n\ncase", (4, 4) => Some(12)); | ||
test_case!("test\n\n\n\ncase", (4, 5) => Some(12)); | ||
test_case!("", (u32::MAX, u32::MAX) => None); | ||
test_case!("", (u32::MAX, u32::MAX) => Some(0)); | ||
} | ||
|
||
#[test] | ||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is #6022, right? And this change brings us in line with VSCode's handling of this edge-case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly vscode behaves the same and the comment is from neovim so they also behave the same