Skip to content
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

java_type_hierarchy: class, method type hierarchy on the quickfix list #512

Closed
wants to merge 1 commit into from

Conversation

lbrayner
Copy link

@lbrayner lbrayner commented Jun 11, 2023

java_type_hierarchy uses java.navigate.openTypeHierarchy and java.navigate.resolveTypeHierarchy to show type hierarchy information of a class or method on the quickfix list.

@lbrayner
Copy link
Author

Please consider adding something like this to nvim-jdtls.

@lbrayner
Copy link
Author

The motivation for this was eclipse-jdtls/eclipse.jdt.ls#2684.

I was looking for a way to jump from an interface method implementation on a class to its declaration on the interface file. java_type_hierarchy also delivers that..

@lbrayner lbrayner force-pushed the type-hierarchy branch 2 times, most recently from 34ec0a4 to 5dc0a45 Compare July 4, 2023 01:45
java_type_hierarchy uses java.navigate.openTypeHierarchy and
java.navigate.resolveTypeHierarchy to show type hierarchy information of
a class or method on the quickfix list.

If there is only one result, jump to it.
@mfussenegger
Copy link
Owner

Type hierarchy is also part of the spec: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_prepareTypeHierarchy

I think eclipse.jdt.ls and neovim core should implement that instead of going with the custom off-spec variant

@mfussenegger
Copy link
Owner

See also eclipse-jdtls/eclipse.jdt.ls#2769

I'm not going to merge the off-spec variant. type hierarchy should be implemented in neovim core instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants