-
I am not sure this is a problem with rust-analyzer, but maybe someone would have an idea where to look for a solution... I am using rust-analyzer (2025-01-28) in NeoVim through
Before that I would only get actions 1 and 2 which is the expected behavior. I have a feeling that this issue is the result of me trying using Copilot yesterday. I've installed the The reason I ask here is that AFAIK code actions list is requested from the LSP server, which is Rust Analyzer in this case. Correct me if I'm wrong. Any ideas how to find the culprit or fix the issue would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
So, this is technically expected behavior in that we do generate a billion of these code actions. The idea is that we have an lsp extension that groups them under one codeaction instead, but if the client doesn't support that, you end up with what you are seeing. I am confused that you are only running into this now as this code action has been like this for a year or more. Either way, I believe, for this code action we should actually disable it if the client does not support the extension as it makes it unmanageable as you've shown. |
Beta Was this translation helpful? Give feedback.
So, this is technically expected behavior in that we do generate a billion of these code actions. The idea is that we have an lsp extension that groups them under one codeaction instead, but if the client doesn't support that, you end up with what you are seeing. I am confused that you are only running into this now as this code action has been like this for a year or more.
Either way, I believe, for this code action we should actually disable it if the client does not support the extension as it makes it unmanageable as you've shown.