-
-
Notifications
You must be signed in to change notification settings - Fork 132
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
Use WorkspaceEdits to apply changes instead of commands #2574
Comments
Thank you. I didn't realize that could be the issue. I'll take a look at fixing it. It currently uses the "rename" command to allow each language server to fix the spelling issue in a language safe way. Clearly the source code commit doesn't need that level of functionality. I'll take a look at changing it to be based upon the scheme and file type. Maybe I missed it, but is there a way to detect when an edit as been applied (with respect to a |
Thanks for the details! You'll have to use workspace edits for the source control input but can continue using When code actions are requested in the source control input box, you should see As for tracking when edits are applied, you can still use a command for this. You just can't use Let me know if you run into any issues making this change. It won't actually work end-to-end until microsoft/vscode#176699 is merged but I'm hoping to get that in early this week |
The spell checker already has a setting: I'm guessing this should work:
"[scminput]": {
"cSpell.fixSpellingWithRenameProvider": false
}, |
If more needs to be done, please re-open or create a new issue. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
👋 Hi, I work on VS Code's code action support
We're currently working to enable code actions inside of the source control commit message box: microsoft/vscode#176699. However I noticed that even after turning on this functionality in VS Code, the quick fixes generated by this extension do not work properly
The root cause seems to be that this extension uses commands to apply fixes. If you instead switch to use a
WorkspaceEdit
on your code actions (CodeAction.edit
), you quick fixes should start working the source control input. Workspace edits also don't require an extra roundtrip to the server so they should be faster to apply too!Let me know if you have any questions about this change. Keep an eye on microsoft/vscode#176699 to see when source control input quick fixes are enabled in VS Code
The text was updated successfully, but these errors were encountered: