Checking for null capabilities. #7921
Merged
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
lahodaj
added
Java
|
Thank you so much. |
sid-srini
added a commit
to sid-srini/javavscode
that referenced
this pull request
Oct 29, 2024
… only Backported apache/netbeans#7921 to fix unit tests breakage due to uninitialised `NbCodeClientCapabilities.getClientCapabilities()` by adding a null check in the initialisation of `lineFoldingOnly` in `TextDocumentServiceImpl.foldingRange()`. Signed-off-by: Siddharth Srinivasan <[email protected]>
dbalek
approved these changes
Oct 29, 2024
|
Thanks for the review! |
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.
We unfortunately broke the
ServerTestwith:#7750
This patch tries to account for capabilities that are
null. I believeclient.getNbCodeCapabilities()never returnsnull, butclient.getNbCodeCapabilities().getClientCapabilities()does, currently.