-
Notifications
You must be signed in to change notification settings - Fork 148
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
Why is WorkspaceEditCapabilities
's constructor setting documentChanges
is deprecated?
#822
Comments
Although it is indeed unclear why this constructor was deprecated, I'd be inclined to just remove it now. There are as many as five properties in @jonahgraham WDYT? |
If you don't wanna to introduce a breaking change for nothing, then it would be better to maybe start by providing a description in the deprecation annotation 😅 |
See conversation in eclipse-lsp4j#822 (comment)
See conversation in eclipse-lsp4j#822 (comment) Fixes eclipse-lsp4j#822
See conversation in #822 (comment) Fixes #822
I added some documentation based on this conversation. We can remove the deprecated code at some point, but I recommend we do that around the time we update to soon to be released (I assume?) LSP 3.18 spec. |
See this constructor:
lsp4j/org.eclipse.lsp4j/src/main/java/org/eclipse/lsp4j/Protocol.xtend
Lines 107 to 110 in cc20058
It is unclear why it was deprecated. This deprecation notice has been added in commit 43a0e07, seemingly after a review in #277 and deprecation of
Boolean resourceChanges
member of the same type.Perhaps @yaohaizh just mistaken
resourceChanges
anddocumentChanges
while doing that? Anyway, I think it's a good idea to add an explanation to the deprecation notice (it looks like you can just safely usesetDocumentChanges
instead). Optionally, we may un-deprecate the constructor in question.The text was updated successfully, but these errors were encountered: