-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
add type hierarchy provider #128667
add type hierarchy provider #128667
Conversation
1dee4d9
to
df29c45
Compare
src/vs/workbench/contrib/typeHierarchy/browser/typeHierarchy.contribution.ts
Show resolved
Hide resolved
Signed-off-by: Yan Zhang <[email protected]>
df29c45
to
8135848
Compare
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.
Some nit, enforcing proposed API is the most important
Thanks, this is looking pretty good already |
Signed-off-by: Yan Zhang <[email protected]>
Signed-off-by: Yan Zhang <[email protected]>
Signed-off-by: Yan Zhang <[email protected]>
Signed-off-by: Yan Zhang <[email protected]>
Signed-off-by: Yan Zhang <[email protected]>
Thanks @Eskibear |
fyi - I have pushed f50840e which adds an API command test.
There was actually a bug in call hierarchy that also made it into the type hierarchy. This should be resolved now which is goodness. Using the call hierarchy in the references viewlet should now be possible |
This PR is part of Type Hierarchy API.
corresponding LSP proposal in microsoft/language-server-protocol#1231
early investigation here: microsoft/vscode-languageserver-node#779
This PR includes: