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
Per survey feedback, I'm creating a mega issue for all code completion smartness improvements.
A few things that customers already ask:
Theme: existing commands from other products
- sout / syso : prints System.out.printIn()
- soutm: adds the current class and method names
- soutp: adds method parameter names and values
- soutv: adds the last variable value
- Sc -> Scanner
Theme: Provide better revelance when working in specific projects
- Java AWT packages missing when working on GUI applications
- Anything else that can improve the relevance
Theme: Code-sensitive code completion check
- Optimize for different cases of code blocks
- Don't display ElementScanner when user just types all lower case letters "else"
Theme: Enum case auto-generation
- Generate switch cases for all enum values
Theme: Array
- Auto complete code snippet int[n][n] - > new int[n][n]
Theme: Main function
- When user types public static void main, it shouldn't generate main function signature twice
Theme: Generic arguments
- More intelligent <> completion (such List<> )
Theme: Signature Help Improvement
- “When I calling a method, intellisense displays the parameters only ONE time. Basically, it displays the parameters, then as I start putting the values for those parameters, the parameters list disappears”
Hi nickzhums, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Here are some pointers for the various code-completion enhancements you mentioned:
• Existing live templates (sout, syso, soutm, Sc) are tracked in “Optimize auto code completion experience for IntelliJ and Eclipse users”:
– #772
• Preventing duplicate text on completion (e.g. avoiding double main signatures or overwriting existing tokens) is discussed in:
– microsoft/vscode-java-debug#1394
This covers “contextual insert” and could help with your “main function” and code-sensitive completion themes.
• Smarter method-argument guessing (filling with parameter names when no variables exist) lives under eclipse.jdt.ls’s guessMethodArguments feature:
– eclipse-jdtls/eclipse.jdt.ls#2512 (comment)
• For enum-switch-case generation, array-snippet expansions, generic <> completions, and signature-help persistence, there aren’t direct existing issues—consider opening separate feature requests in the vscode-java-pack or vscode-java repo so they can be individually triaged.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
Activity
nickzhums commentedon Nov 19, 2021
adding Sheng Chen (@jdneo) to be the main PoC for this effort
nickzhums commentedon Dec 1, 2021
Another case:
https://microsoft-my.sharepoint.com/personal/v-laurelgui_microsoft_com/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fv%2Dlaurelgui%5Fmicrosoft%5Fcom%2FDocuments%2FRecordings%2FE2E%20Journey%20Study%20%2D%20Sanketh%2Emp4&parent=%2Fpersonal%2Fv%2Dlaurelgui%5Fmicrosoft%5Fcom%2FDocuments%2FRecordings
53:00
nickzhums commentedon Feb 23, 2022
Per our discussion, we could also look at IntelliJ Settings -> Editor -> Live Templates Sheng Chen (@jdneo)
github-actions commentedon Oct 31, 2025
Hi nickzhums, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Here are some pointers for the various code-completion enhancements you mentioned:
• Existing live templates (sout, syso, soutm, Sc) are tracked in “Optimize auto code completion experience for IntelliJ and Eclipse users”:
– #772
• Preventing duplicate text on completion (e.g. avoiding double
mainsignatures or overwriting existing tokens) is discussed in:– microsoft/vscode-java-debug#1394
This covers “contextual insert” and could help with your “main function” and code-sensitive completion themes.
• Smarter method-argument guessing (filling with parameter names when no variables exist) lives under eclipse.jdt.ls’s guessMethodArguments feature:
– eclipse-jdtls/eclipse.jdt.ls#2512 (comment)
• For enum-switch-case generation, array-snippet expansions, generic
<>completions, and signature-help persistence, there aren’t direct existing issues—consider opening separate feature requests in the vscode-java-pack or vscode-java repo so they can be individually triaged.Other references with low confidence
• Java debug console debounce causing stale completions (debugger only): microsoft/vscode-java-debug#817 (comment)
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!