-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
add support for LSP workspace/executeCommand message for initial use with Scala Metals #3300
Comments
Would like to know about it also. As a starting point, I would imagine the following might be relevant?
|
Having done more research, Metals' http approach is there only as a fallback for users when their LSP client doesn't support
@zoonfafer ... I agree that adding standard LSP client support for We would also need to update the capabilities here: Lines 361 to 371 in 2b78568
Given this change would add capabilities relevant for any LSP server that ALE can handle, I think it's reasonable to ask for @w0rp 's thoughts... @w0rp : does the above approach seem reasonable? |
Sending the |
this is will also be really helpful for starting the eclipselsp DAP, right now vimspector are using YCM to do this one, but this could be made possible by ALE:
|
I'm using Metals via https://github.com/dense-analysis/ale/blob/master/ale_linters/scala/metals.vim (thanks, @zoonfafer!)
Metals needs users to import the build upon first use within a workspace (i.e., a Scala project). Once you do that, the Metals server exposes all the goodies necessary for a rich user experience.
To tell the Metals server to import the build, you
POST
to its/execute-command
endpoint withcommand=build-import
:curl -XPOST http://localhost:5031/execute-command?command=build-import
The first time one does this in a project, it takes a while. Subsequent invocations take much less time.
Is there some standard pattern for this sort of thing in ALE's plugin ecosystem?
The text was updated successfully, but these errors were encountered: