-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
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
Duplicate client/registerCapability for workspace/executeCommand #937
Comments
angelozerr
added a commit
to angelozerr/lemminx
that referenced
this issue
Nov 29, 2020
Fixes eclipse#937 Signed-off-by: azerr <[email protected]>
angelozerr
added a commit
to angelozerr/lemminx
that referenced
this issue
Nov 29, 2020
Fixes eclipse#937 Signed-off-by: azerr <[email protected]>
@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. |
angelozerr
added a commit
that referenced
this issue
Jan 5, 2021
Fixes #937 Signed-off-by: azerr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: