You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for typeHierarchy/supertypes and typeHierarchy/subtypes and integrate those via the codeInsight.gotoSuper and codeInsight.lineMarkerProvider EPs.
#652
Open
SCWells72 opened this issue
Dec 1, 2024
· 3 comments
JetBrains' IDEs provide extensive support for navigating up and down type hierarchy relationships. Some of this is already integrated via LSP4IJ, e.g., Go To Implementation(s) via #636, but others are missing. Minimally support for typeHierarchy/supertypes should be added and integrated into the IDE via the codeInsight.gotoSuper EP. I'm not sure whether or not typeHierarchy/subtypes would add much vs. what is already used for Go To Implementation(s).
Additionally it would be nice to add support for type/method hierarchy relationships in the editor gutter area via codeInsight.lineMarkerProvider and the information from these LSP features to provide clear visual representations of these type inheritance relationships.
The text was updated successfully, but these errors were encountered:
Go To Super is actually Ctrl+U (Windows/Linux). Do you know if TypeScript supports typeHierarchy/supertypes? If not, this becomes less compelling for me, but it's certainly still useful for languages which do support these notions.
JetBrains' IDEs provide extensive support for navigating up and down type hierarchy relationships. Some of this is already integrated via LSP4IJ, e.g., Go To Implementation(s) via #636, but others are missing. Minimally support for
typeHierarchy/supertypes
should be added and integrated into the IDE via thecodeInsight.gotoSuper
EP. I'm not sure whether or nottypeHierarchy/subtypes
would add much vs. what is already used for Go To Implementation(s).Additionally it would be nice to add support for type/method hierarchy relationships in the editor gutter area via
codeInsight.lineMarkerProvider
and the information from these LSP features to provide clear visual representations of these type inheritance relationships.The text was updated successfully, but these errors were encountered: