Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Remove Redundant Type Hierarchy

Aberta
  • Algo errado?
#4,560 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@MeherSru já está trabalhando nisso.

Desde 28/10/2026.

  • #4565 de @MeherSru — aberto

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
66/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript, vscode
Domínio
tooling

Direção de pesquisa

Start in package.json and find the command IDs and menu contributions for the custom type hierarchy, then grep those IDs across the extension. Read typeHierarchyTree.ts and references-view.d.ts to see what can be deleted, and check the command implementations registered elsewhere. Done means the duplicate "Show Type Hierarchy" entry is gone, the custom commands and UI code are removed, and the extension builds and tests pass.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug

Describe the bug
Currently, when you right click a class name, there are two context menu entries called "Show Type Hierarchy".

One is contributed by us (vscode-java) and one is a default one provided by VS Code.

We should remove the entry provided by us, along with all the associated UI code, since the default type hierarchy UI provided by VS Code is sufficient, and removing code with reduce the complexity of this project. VS Code provides this UI automatically, since jdtls advertises it supports type hierarchy. The other entry exists because we implemented type hierarchy support before it was added into the LSP specification.

There is one minor difference between our custom type hierarchy UI and the default UI: we provide a "Class Hierarchy" view that shows both super classes and sub classes at the same time. However, after talking this through with Rob, I don't think it's worth saving this UI, since then there would be two different ways to access the same information, which would be confusing to end users.

Here's a list of things we'll need to remove: (hopefully complete but there might be other things as well):

  1. The UI itself, i.e. typeHierarchyTree.ts
  2. The typings we have for interacting with VS Code's references view API (references-view.d.ts)
  3. The commands to open the type hierarchy view (these are registered in package.json and implemented throughout the codebase; grepping for the id listed in the package.json should find the implementations)
  4. The registration of various commands (also in the package.json)
  5. There's separate "Subtype hierarchy" and "Supertype hierarchy" commands that are referenced in code, but only appear in the command palette and currently don't seem to function. These should be removed

See https://github.com/redhat-developer/vscode-java/pull/2376 for some more context

To Reproduce
Steps to reproduce the behaviour:

  1. Make a type that inherits from a few other types:
public class B extends A implements Serializable {

}
  1. Right click on the type name (in this case B).
  2. There are two "Show Type Hierarchy"

Expected behaviour
There should instead be one "Show Type Hierarchy" entry

Environment

  • Operating System: Linux (but it's not Linux specific)
  • JDK version: 25
  • Visual Studio Code version: 1.143.1
  • Java extension version: 1.59.0

Additional Information

Linguagem predominante
TypeScript
Estrelas
2.3k
Forks
549
Merge médio
4d 21h
PRs com merge (30d)
19

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de redhat-developer/vscode-java

Todas as issues de redhat-developer/vscode-java

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.