Handle methods with Void return types properly #675
Merged
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.
The DAP part of LSP4J was being too strict and failing to parse response objects for methods with Void return type. With Java 17 (or some version since Java 11) turning on more strict reflection rules, the "An illegal reflective access operation has occurred" that used to be a warning is now an exception like "Failed making constructor 'java.lang.Void#Void()' accessible"
This change makes the code work and compatible with how LSP4J handles LSP Void return types.
Fixes #674