Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#18 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
java, typescript, vscode
Ambito
developer-experience, tooling

Direzione di ricerca

Inizia leggendo ide/editor/src/org/netbeans/modules/editor/resources/NetBeans-preferences.xml e confronta la relativa impostazione completion-auto-popup-delay con il percorso org-netbeans-modules-editor-settings-CustomPreferences.xml dell'estensione. Riproduci il ritardo sia in NetBeans IDE sia nell'estensione VSCode, quindi determina se è fattibile una singola modifica a una preferenza con ambito ristretto. Il lavoro è completato quando il comportamento supportato e l'ambito sono chiari, con un test riproducibile o una limitazione documentata.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
11
Fork
13
Merge medio
2g 18h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/netbeans-vscode

Tutte le issue di apache/netbeans-vscode

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.