Deserialization support for AWS LSP extended InitializeResult #49
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.
Description of changes:
AWS Flare LSPs extend the basic LSP
InitializeResult
with extended metadata, such as available chat commands. By default these additional properties are lost by LSP4j's deserialization logic. This change models the extended type and registers in a custom type adapter for GSON (LSP4j's deser library) to deserialize into the extended type and therefore surface the properties.Keep in mind that there may be additional properties that need to be modeled to the extended
InitializeResult
, but I am illustrating the pattern for accessing the chat commands here.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.