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
I've encountered an issue with blink.cmp where the completion suggestions provided by yaml-language-server (yamlls) include server-side placeholders that behave like snippets. This creates a suboptimal user experience because these placeholders:
Are inserted automatically during completion.
Trigger further completions in a snippet-like way, even if snippets are not explicitly enabled (capabilities.textDocument.completion.completionItem.snippetSupport = false)
For example:
As you can see, on the second screenshot, it's not blink.cmp suggestions
While editing a YAML file, when completing kind property (kubernetes), the server provides a placeholder-like snippet (e.g.).
Accepting this suggestion inserts the placeholder.
Expected Behavior
I would like to intercept or completely disable this behavior, ensuring that server-side snippets or placeholder completions do not interfere with the editing experience in blink.cmp?
Question
Is there currently a way to configure blink.cmp to detect and ignore these server-side placeholders or snippet-like suggestions? Or is it something that should be handled by LSP?
Context
This issue seems specific to yaml-language-server as it includes these placeholders by default. Disabling snippet support via the capabilities configuration or modifying the server settings (e.g., disableDefaultProperties or disableAdditionalProperties) does not resolve the problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've encountered an issue with
blink.cmp
where the completion suggestions provided byyaml-language-server
(yamlls
) include server-side placeholders that behave like snippets. This creates a suboptimal user experience because these placeholders:capabilities.textDocument.completion.completionItem.snippetSupport = false
)For example:
As you can see, on the second screenshot, it's not
blink.cmp
suggestionskind
property (kubernetes), the server provides a placeholder-like snippet (e.g.).Expected Behavior
I would like to intercept or completely disable this behavior, ensuring that server-side snippets or placeholder completions do not interfere with the editing experience in
blink.cmp
?Question
Is there currently a way to configure
blink.cmp
to detect and ignore these server-side placeholders or snippet-like suggestions? Or is it something that should be handled by LSP?Context
This issue seems specific to
yaml-language-server
as it includes these placeholders by default. Disabling snippet support via the capabilities configuration or modifying the server settings (e.g.,disableDefaultProperties
ordisableAdditionalProperties
) does not resolve the problem.I believe this
yaml-language-server
issue could be related to this redhat-developer/yaml-language-server#161Any guidance on how to handle this scenario within
blink.cmp
would be greatly appreciated.Beta Was this translation helpful? Give feedback.
All reactions