Closed kittaakos closed 5 years ago
LSP4J also allows to declare multiple remote service interface, which can be useful in case your extension does not inherit from LanguageClient. While we're at it, should we also support that, or do you think that's unnecessary?
should we also support that, or do you think that's unnecessary?
I would cover it when we have the use-case.
While we're at it
What somewhat bugs me is why did I have to change the code at two different places? Perhaps we can extract the common code within this PR. What do you think?
What somewhat bugs me is why did I have to change the code at two different places? Perhaps we can extract the common code within this PR. What do you think?
If you have an idea for doing it, sure!
I have updated the PR and exposed the client class in the server setup so both launchers can use it.
Out of curiosity; should I avoid "fixing" the whitespaces in the future or not? I can revert the whitespace changes for this PR too.
Thanks for the patch, @kittaakos.
In this repo we don't care that much about whitespace. Editing Xtend files in Eclipse usually adds the TABS to empty lines, and formatting would remove them.
Closes #13.
Signed-off-by: Akos Kitta kittaakos@typefox.io