Add custom client capability registration. #1013
Merged
Conversation
This file contains hidden or 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
Metals requires a set of experimental client capabilities to be sent to the lsp server to enable the treeview provider. client capabilities can be registered as part of the lsp-client definition and sent during initialisation.
Member
|
Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Metals requires a set of experimental client capabilities to be sent to the lsp server during initialisation to enable the treeview provider. In order to decouple the implementation within lsp-treemacs from lsp-mode a new lsp--client field allows the caller to specify additional client capabilities that can be sent along with the standard lsp-mode defined set. Currently these are simply additional capabilities appended to the existing fixed caps.