Open jacksonludwig opened 3 years ago
There should a callstack somewhere (most likely in lsp-log) or you will be able to see it by setting lsp-print-io to t and using lsp-workspace-show-log. I think in the end it is a server bug, I am seeing it too from time to time.
Describe the bug When triggering
lsp-execute-code-action
on code while the cursor is on an operator, e.g.->
or.
, there is an internal error from the language server. I think this only happens in functional stuff likemap
. This doesn't always happen and unfortunately I have yet to find exactly what triggers it.To Reproduce For example, take the following code and try to trigger a code action while the cursor over the lambda operator.
Expected behavior Code action should trigger normally.
Screenshots