-
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
GH-272: Updated the API to support type hierarchies. #273
Conversation
@kittaakos is this PR outdated? microsoft/vscode-languageserver-node#425 has been closed and microsoft/vscode-languageserver-node#426 looks a bit different. |
Yes.
Where do you see the difference? I must have overlooked something. |
export interface TypeHierarchyCapabilities {
/**
* The text document client capabilities.
*/
textDocument?: {
/**
* `true` if the language client supports super- and subtype hierarchies. Otherwise, `false` or `undefined`.
*/
typeHierarchy?: boolean;
}
} vs. https://github.com/eclipse/lsp4j/pull/273/files#diff-d10742f66bf9c4b629c5e8252db884ba class TypeHierarchyCapabilities {
/**
* The language client supports super- and subtype hierarchies.
*/
Boolean typeHierarchy
new() {
}
new(Boolean typeHierarchy) {
this.typeHierarchy = typeHierarchy
}
} The first is just a Boolean, the second wraps it in an object. |
3e60964
to
27fa044
Compare
I have updated the PR based on this microsoft/vscode-languageserver-node#346 (comment). |
org.eclipse.lsp4j/src/main/java/org/eclipse/lsp4j/Protocol.xtend
Outdated
Show resolved
Hide resolved
Closes: eclipse-lsp4j#272 Signed-off-by: Akos Kitta <kittaakos@typefox.io>
Signed-off-by: Akos Kitta <kittaakos@typefox.io>
Fixes eclipse-lsp4j#273 Signed-off-by: azerr <azerr@redhat.com>
Added a method
Closes: #272
Signed-off-by: Akos Kitta kittaakos@typefox.io