-
Notifications
You must be signed in to change notification settings - Fork 375
Support WorkspaceEditMetadata in workspace/applyEdit
#1390
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
Conversation
|
@dbaeumer, I'm guessing that you missed this when you got back from vacation. |
dbaeumer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also add a capability to WorkspaceEditClientCapabilities (e.g. metaDataSupport).
We would also need a PR against the 3.18 spec here:
|
@dbaeumer, thanks for taking this change. Any guess as to when your next release will be available? |
|
I want to get the snippet support in as well before having a new release. This however requires the new VS Code release that is due this week. So a new LSP release will not arrive before next week. |
To fix microsoft/pylance-release#5217 (comment) in Pylance, I'd need the
Workspace.applyEditcall inhandleApplyWorkspaceEditto pass{ isRefactoring: true }as the second parameter.Is it reasonable to add
WorkspaceEditMetadatatoworkspace/applyEdit, soisRefactoringcan be sent optionally via LSP?