-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Code actions of kind 'quickfix 'requested but returned code action is of kind 'refactor.extract.variable'. #4211
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
Comments
Oh interesting vscode must send the context down now with the |
I think this may be a bug in vscode or vscode-languageclient |
I've seen a similar message but in a different context. If this doesn't belong in this issue, please tell me and I'll post a new issue. In
This causes VSCode to reformat a document before saving it. The exact message I'm getting is this:
The message appears every time I save a document. Also, I must mention that sometimes, when I save, VSCode shows a popup in the lower-right that says It looks like the rust-analyzer extension doesn't check for the kind of actions that is being requested and returns them all, and I suspect that this is what causes saving to be slow. In my project, the "Quick Fix..." command ( I'm using |
We do not categorize most code actions yet (though we advertise all of them) so we ignore the filter on the server and miss that optimization (you see the results of this delay). The client-side filters out any code actions not requested. |
@kjeremy this might be fixed now? |
The underlying issue hasn't changed so I don't expect it to be fixed. We now categorize our code actions but still do not filter them. |
Not sure is this a duplicate or should I open a new issue, but for me the
DetailsThe unusual part is that I'm on NixOS, but I see that you patch the binary, that's actually really cool, thanks for that! Using the bundled+patched one. Extension version: v0.3.1162 VSCode about page:
|
same here |
Spotted in the extension host log channel:
The text was updated successfully, but these errors were encountered: