You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I considered dropping down to this lower level library until the issue mentioned above is resolved, but the README seems to have incomplete documentation regarding VSCode integration.
It basically just assumes elm-language-client-vscode is working and refers you to that.
It would be nice to have docs explaining how to get elm-language-server up and running with VSCode. My use case is just to hold me over, but I'm sure other people have use cases as well.
The text was updated successfully, but these errors were encountered:
Ah, well that's a bummer. That's surprising, considering Microsoft invented LSP as a direct result of lessons learned building VSCode. Granted, I still know very little about LSP in general, so take anything I say with a grain of salt.
Well, I guess vscode "suffers" from always getting a first party vscode addon due to it being invented there? I guess nobody had a reason to create a generic implementation. :/
I've been having issues with elm-language-client-vscode, and I recently opened up this issue.
I considered dropping down to this lower level library until the issue mentioned above is resolved, but the README seems to have incomplete documentation regarding VSCode integration.
It basically just assumes elm-language-client-vscode is working and refers you to that.
It would be nice to have docs explaining how to get elm-language-server up and running with VSCode. My use case is just to hold me over, but I'm sure other people have use cases as well.
The text was updated successfully, but these errors were encountered: