redhat-developer / redhat-developer/vscode-java

"Show Call Hierarchy" should have the ability to filter calls, or apply name filter patterns

Abierto
#2,179 3 comentarios 4 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

enhancement navigation upstream
Lenguaje dominante
TypeScript
Estrellas
2.3k
Forks
546
Merge medio
20 h 1 min
PR fusionados (30 d)
11

Descripción

When I use Show Call Hierarchy on a property in a Java class object that is frequently used in both the main source code, as well as in the unit tests, the Call Hierarchy list would display a bunch of results. Because, the results include both the main source code and unit tests references, there isn't a way to automatically exclude certain folder directories or paths out from unwanted invocations.

I would like to request for the feature to apply any one of the following options:

  • Filter test codes. (unit test codes, or codes residing under src/test/java)
  • Apply name filter patterns. (Only includes reference names that matches the given filter patterns.)
  • Limit the call depth of a given number. (Only goes down in depth up to the given number, inclusive.)

This feature is similar to Eclipse's "Filter Calls" dialog:

image

This is accessed by invoking "Show Call Hierarchy" on a class member, then opening "Filters" in the "More Options" menu in Eclipse IDE.

Currently, we don't have anything similar to this in Visual Studio Code with RedHat Java extensions installed.

Environment
  • Operating System: Ubuntu 20.04.2 LTS
  • JDK version: AdoptOpenJDK 11 (jdk-11.0.11+9)
  • Visual Studio Code version: 1.61.2
  • Java extension version: v1.0.0 (October 19, 2021)
Steps To Reproduce
  1. Open any Java class object whose object is used in both the main source code, as well as in the unit test codes.
  2. On any identifiers (method name, class field name, etc.), do SHIFT+ALT+H to invoke "Show Call Hierarchy".
  3. Observe in the list, notice how there aren't any options available to filter certain call invocations from the results. You would have to manually click on the "X" button to remove the entry you don't want, one by one.
Current Result

The "Show Call Hierarchy" looks something like this.

image

Expected Result

After filtering out either all test codes, or applying a name filter pattern to exclude any references containing "test", it should look something like this:

image

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza en el punto de entrada Show Call Hierarchy de la VS Code Java extension y revisa cómo se presentan sus resultados. Compara el filtrado solicitado del código de prueba, los patrones de nombres y el límite de profundidad de llamadas, y determina después el alcance aceptado. Se considera terminado cuando el comportamiento de filtrado elegido está disponible desde la call hierarchy UI y cubre el caso de uso indicado.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java, typescript, vscode
Área
devtools
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.