Supports TextDocumentContentChangeEvent#getRangeLength with null value #1696
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
angelozerr
requested changes
Nov 3, 2024
org.eclipse.lemminx/src/main/java/org/eclipse/lemminx/commons/TextDocument.java
Outdated
Show resolved
Hide resolved
angelozerr
changed the title
|
Thanks @jmatss ! |
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.
Fixes #1674.
Removes the usage of the deprecated
TextDocumentContentChangeEvent.rangeLength. The length of the range is now calculated from theTextDocumentContentChangeEvent.rangeinstead, which should produce the same result.This fixes a NullPointerException that happened when the LSP client didn't set the
rangeLength(which is allowed according to the LSP specification).