Go to symbol in Editor should have a way to include inheritted symbols

One piece of functionality that would be nice to have with VS Code Java is the ability to quickly see all inherited methods of a class that is opened. I can see the ones it declares only. The closest existing functionality would be the Go to symbol in Editor command. This is often useful when exploring some class that has a deeper inheritance structure.

Eclipse has this behaviour through the Quick Outline (<ctrl> + o), when triggered twice, which will additionally show all members that are inherited by the opened type. The outline takes into account cursor positions so it can show an outline for nested classes while completely ignoring the other elements in the document.

[gayanper]

Yes thats what i found as well. So may be this could be presented in the reference-view which is used for type hierarchy and call hierarchy as well ?

The reason i thought like that is, from vscode design language it seems document symbol is just to view the symbols in the current document, a quick access to outline. So showing symbols in the super classes seems to be out of scope of this design language.

So may be looking at the class hierarchy with its symbols should be different feature and since its important for java (at least since most of the java IDEs has it) we could implement is as a view.

Its like super type hierarchy with symbols kind of a view.

WDYT @rgrunber ?

[gayanper]

This might be a preference, but I have always found ctr + o + type immediately in the search filter + <Enter> to be faster/preferrable to using the outline view and clicking on the symbol. Maybe because I never liked the amount of space the outline view takes from the editor. With that said, you’re right, that the outline view should also be changed, so maybe we can start with that for now.

Not sure if you misunderstood me in my previous comment. I think for vscode outline also we cannot distinguish if the documentSymbol call is from outline or quick access popup right ? The outline will ask the symbol information hierarchically and we can use that as a hint. I was suggesting to present this in the reference view which is added from vscode-java. But did you had something else in mind ?

Also, I think those developing language servers that have a notation of “includes” directives would run into the same issue. They’d want to display some symbols that are in a separate document as being part of the current one. So that’s what makes me think that the “documentSymbols” concept is going to have to evolve eventually.

Yes we can raise a improvement for LSP project.