Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Auto Completion Fixes/Enhancement in both the IDE and VSCode Extension

Abierto
  • ¿Algo no está bien?
#18 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
java, typescript, vscode
Área
developer-experience, tooling

Línea de trabajo

Comienza leyendo ide/editor/src/org/netbeans/modules/editor/resources/NetBeans-preferences.xml y compara su configuración completion-auto-popup-delay con la ruta org-netbeans-modules-editor-settings-CustomPreferences.xml de la extensión. Reproduce el retraso tanto en NetBeans IDE como en la extensión de VSCode y determina después si es viable realizar un único cambio de preferencia con un alcance limitado. Se considera completado cuando el comportamiento compatible y el alcance están claros, con una prueba reproducible o una limitación documentada.

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

Descripción

Description

There is a noticeable delay in the AutoCompletion popup in both NetBeans IDE and the NetBeans VSCode Extension. After investigation, it appears the delay originates from the default value of "completion-auto-popup-delay", which is set to 250 ms in the upstream NetBeans codebase:

ide/editor/src/org/netbeans/modules/editor/resources/NetBeans-preferences.xml

Manually overriding this value to 0 in:

%APPDATA%\NetBeans<version>\config\Editors\text\x-java\Preferences\org-netbeans-modules-editor-settings-CustomPreferences.xml

successfully removes the latency in NetBeans IDE.

However, applying the same change in the VSCode extension under:

C:\Users<User>.vscode\extensions\asf.apache-netbeans-java-27.0.1\nbcode\nbcode\config\Editors\text\x-java\Preferences\org-netbeans-modules-editor-settings-CustomPreferences.xml

does not affect auto-completion behaviour, suggesting the extension may not read or honor this preference.

There are also related settings such as "javadoc-popup-next-to-cc" that appear configurable in the IDE but are not exposed or functional within the VSCode extension.

Additionally, some NetBeans IDE–specific features (for example, Maven Plugin Goals UI and pom.xml IntelliSense) are not available in the extension, and it is unclear whether this is by design, a technical limitation, or related to project scope.

Use case/motivation

  • Reducing the completion popup delay significantly improves responsiveness and overall user experience, especially for users accustomed to real-time IntelliSense.

  • Ensuring the VSCode extension respects the same configuration options as the IDE provides consistency across NetBeans tooling.

  • Exposing IDE-like settings (popup delays, JavaDoc popup behaviour, completion timing) would make the VSCode extension more appealing and usable for developers who prefer VSCode but rely on NetBeans’ Java capabilities.

  • Clarifying the intended scope and limitations of the VSCode extension helps contributors understand what enhancements are feasible and welcome.

Related issues

  1. Should the default completion popup delay be reduced to 0 upstream?
    The current default of 250 ms introduces noticeable sluggishness. I am willing to submit a PR for this change if it is acceptable.

  2. Does the VSCode extension intentionally ignore or bypass the editor settings stored in the "org-netbeans-modules-editor-settings-CustomPreferences.xml" files?
    If so, is there an alternative way to configure the behaviour of auto-completion within the extension?

  3. Why are certain IDE settings such as "javadoc-popup-next-to-cc" not exposed or functional in the VSCode extension?
    Is this due to architectural constraints within the LSP implementation, or simply unimplemented?

  4. Why are some IDE-specific features (such as Maven Plugin Goals UI and enhanced pom.xml IntelliSense) missing from the extension?
    Are these features out of scope for the extension's purpose, or is there a technical constraint preventing their inclusion?

Are you willing to submit a pull request?

Yes

Lenguaje dominante
TypeScript
Estrellas
11
Forks
13
Merge medio
2 d 18 h
PR fusionados (30 d)
2

Preparar el entorno

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.

Más de apache/netbeans-vscode

Todos los issues de apache/netbeans-vscode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.