Trip report: polymer-editor-server
See original GitHub issueI’m trying out intellij-lsp
with my language server. It works well with vscode, atom, and sublime text’s LSP plugin, and intellij support is a very common request from our users.
I downloaded IntelliJ IDEA CE 2017.3
, installed intellij-lsp
, and configured my LSP server as a raw command, with a file extension of html
, and the command polymer-editor-service
. From my logs I can see that polymer-editor-service
is started and initialized, and I get onDidChangeWatchedFiles
requests, but that’s pretty much it. I don’t get notifications when files are opened, closed, changed in memory, or any requests for features like hover or completions.
Reproducing this is pretty straightforward if you have NodeJS v6 or higher installed. npm install -g polymer-editor-service
will get you the LSP server, and the simplest way to check if it’s working is to put something like this in an HTML file:
<link rel="import" href="./does-not-exist.html">
It should report an error diagnostic on the url.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (2 by maintainers)
I’m working on a new release of our editor server, should be pretty soon. Our integration tests are passing on windows now. We’re still sending over urls like
file///d%3A/path/to/file.html
as that’s what Microsoft’s ownvscode-uri
encodes, so I think that’s correct, but we had a bunch of other issues with our URIs on Windows so I wouldn’t rule out that bad URIs were still an issue. Will update this thread once our improved URI handling is released.Currently with the latest version of intellij-lsp on MacOS (where our URIs should be correct) it looks like something’s failing before initialization completes. Stack trace:
polymer-editor-service v2.1.0 is out now, and should handle windows URIs correctly now.