We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With regards to sublimelsp/LSP-lemminx#9
It appears LemMinX tries to register workspace/executeCommand twice.
workspace/executeCommand
One instance for xml.validation.current.file and one for xml.validation.all.files command.
xml.validation.current.file
xml.validation.all.files
With a birds eye onto https://microsoft.github.io/language-server-protocol/specifications/specification-3-15 I'd expect one registration message for workspace/executeCommand with commands containing a list of all available commands.
commands
LSP: lemminx: registering capability: codeActionProvider LSP: lemminx: registering capability: completionProvider LSP: lemminx: registering capability: documentHighlightProvider LSP: lemminx: registering capability: hoverProvider LSP: lemminx: registering capability: renameProvider LSP: lemminx: registering capability: definitionProvider LSP: lemminx: registering capability: typeDefinitionProvider LSP: lemminx: registering capability: referencesProvider LSP: lemminx: registering capability: documentFormattingProvider LSP: lemminx: registering capability: rangeFormattingProvider LSP: lemminx: registering capability: documentSymbolProvider LSP: lemminx: registering capability: executeCommandProvider LSP: lemminx: registering capability: executeCommandProvider LSP: executeCommandProvider is already registered at executeCommandProvider.id with ID 8dce5c84-5665-4060-84d6-c58ebedc49d7, overwriting
:: <-- lemminx client/registerCapability(12): {'registrations': [{'registerOptions': {'id': '8dce5c84-5665-4060-84d6-c58ebedc49d7', 'commands': ['xml.validation.current.file']}, 'id': '8dce5c84-5665-4060-84d6-c58ebedc49d7', 'method': 'workspace/executeCommand'}]} :: >>> lemminx 12: None :: <-- lemminx client/registerCapability(13): {'registrations': [{'registerOptions': {'id': '2dbb8863-94a3-45eb-99b9-a78343e3f591', 'commands': ['xml.validation.all.files']}, 'id': '2dbb8863-94a3-45eb-99b9-a78343e3f591', 'method': 'workspace/executeCommand'}]} :: >>> lemminx 13: None
The text was updated successfully, but these errors were encountered:
Duplicate client/registerCapability for workspace/executeCommand
6408e2f
Fixes eclipse-lemminx#937 Signed-off-by: azerr <[email protected]>
Fix duplicate client/registerCapability for workspace/executeCommand
463ff39
@deathaxe I try to fix your issue (very quckly with #938) could you tell meif it work for you. Thanks!
@BoykoAlex could you review my PR please? I needto manage the unregister commands.
Sorry, something went wrong.
c1f855c
Fixes #937 Signed-off-by: azerr <[email protected]>
datho7561
Successfully merging a pull request may close this issue.
With regards to sublimelsp/LSP-lemminx#9
It appears LemMinX tries to register
workspace/executeCommand
twice.One instance for
xml.validation.current.file
and one forxml.validation.all.files
command.With a birds eye onto https://microsoft.github.io/language-server-protocol/specifications/specification-3-15 I'd expect one registration message for
workspace/executeCommand
withcommands
containing a list of all available commands.Console log:
Communication log:
The text was updated successfully, but these errors were encountered: