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
/**
* The primary text to be inserted is treated as a snippet.
*
* A snippet can define tab stops and placeholders with `$1`, `$2`
* and `${3:foo}`. `$0` defines the final tab stop, it defaults to
* the end of the snippet. Placeholders with equal identifiers are linked,
* that is typing in one will update others too.
*/
export const Snippet = 2;
The text was updated successfully, but these errors were encountered:
@evidolob , @JPinkney, I am running into same issue and I noticed that it's part of your roadmap. I don't see any milestone or due date information. Could you please let me know if you have an ETA?
Thanks!
Not entirely sure if we have an ETA at the moment, it just depends on when we get the time to make the changes. Maybe @evidolob will have a timeline when he comes back from PTO
I've also encountered this issue, and I must say that the current behavior is not very user-friendly. Specifically, I want to be able to disable this behavior entirely. The problem lies in how the server suggests placeholders and subsequently provides further completions in a snippet-like manner, which is not desirable in my workflow.
It would be great if there were a simple configuration option to disable server-side snippet suggestions, particularly for placeholder completions. This would make the language server much more customizable and user-friendly for various development environments.
Thank you for your work on this project, and I hope this feedback helps improve the experience for other users as well.
The completion request always returns snippet-type completions, even if the client initialisation request doesn't claim to support them.
Logs:
snippetSupport: true
which should be interpreted as not supporting snippets (only plaintext)Note:
"insertTextFormat":2
is 'snippet' :The text was updated successfully, but these errors were encountered: