Ivan Yonchovski

I think it most likely narrows down to what @muirdm mentioned: > perhaps by adding a function to invoke this kind of code action similar to lsp-organize-imports @muirdm > Have...

Seems like we should change lsp--text-document-code-action-params which ATM returns only the diagnostics on the current line/region. What we should most likely do is to check if this is fix-all request...

Then I guess we should check what vscode does. Fix all might be working only on the region(we have the expected behavior) while eslint for which fix all is much...

@kiennq FYI it reproduces with lsp-start-plain.el

> @kiennq FYI it reproduces with lsp-start-plain.el disregard that, I though that I am in another issue.

We can and it is easy to do so. The concern is the granularity - because it might suppress useful messages as well. We may introduce "level". 0 means log...

IIUC one solution for you would be to write a wrapper over lsp function and put the logic that you want in that wrapper. You may take a look at...

JDT fails to import the project and then returns wrong organize imports actions. I believe it is related to https://github.com/eclipse/eclipse.jdt.ls/issues/871 ``` Could not run build action using Gradle distribution 'https://services.gradle.org/distributions/gradle-5.0-all.zip'....

When I do this, the issue with textEdit goes away but then the server sends bad additionalTextEdit. ``` [Trace - 08:30:09 AM] Received response 'completionItem/resolve - (5922)' in 0ms. Result:...

To elaborate a bit more: note that RA range includes `a.` without `letm` while the jdtls includes `s.nnull`. For both the completion is requested after `s.nnull` and `a.letm` respectively.