In VSCode extension added user configuration for commit characters for accepting code suggestions#8515
Conversation
…r accepting code suggestions
|
Not sure what @dbalek thinks here, but thinking of this for a bit: I am not sure that forcing the same list of commit characters on all completion items is ideal. E.g. there may be some items where it may make sense to confirm them on Maybe one of these would work better:
|
|
Going back to this - thinking of this more, the actual commit characters sent out from the server should probably be an intersection between the commit characters requested by the completion item, and the user-selected commit characters. That would make most sense to me. |
Yes, this approach would be better, however even in NetBeans, all |
|
I was digging a little bit more on how this works in NetBeans, and it turns out that whatever is in the settings is used unconditionally for all completion items, except for So, ultimately, we can go with the patch as proposed here, I think. |
|
FWIW, the existing filter is here: |
|
Unless there are objections, I would like to integrate in a few days. |
This PR adds support for configurable commit characters in the Java LSP server. Users can now define which characters (e.g., ., ,) trigger the acceptance of a code completion suggestion via the new
netbeans.java.completion.commit.charssetting in the Netbeans VS Code extension. The server reads this configuration and applies the characters to completion items dynamically. This improves the flexibility and user control over the code completion behaviour.