-
(This might be out of scope for this plugin specifically) I often find myself looking through classes and file structure of my dependencies to look at the API or figure out how specific things are done in provided examples and library classes (sources). It would be really helpful if there was a way to look at all dependencies/libraries at a glance and traverse through them in some kind of tree (maybe even an extension to neo-tree). How do you tackle such a situation? Could we have a system in place for |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 1 comment 2 replies
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Found some projects that might be helpfulhttps://github.com/uzxmx/coc-java-dependency andhttps://github.com/Microsoft/vscode-java-dependency. The latter one is a jdtls extension, and hopefully we can just plug it into Edit : Other related projects that might also be helpfulhttps://github.com/microsoft/vscode-gradle &https://github.com/Microsoft/vscode-maven. I couldn't see specific classes/files being accessed through these, but be helpful for implementation or something |
BetaWas this translation helpful?Give feedback.
All reactions
-
Thanks. This is not possible right now but adding this to the backlog. It should be possible to use neo-tree as the view. You can view them here but this will not be implemented soon |
BetaWas this translation helpful?Give feedback.
All reactions
-
https://github.com/JavaHello/java-deps.nvim could be the option... but... they suggest: I don't know how to get the root_dir in nvim-java :( |
BetaWas this translation helpful?Give feedback.