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
Language servers such as vscode-css, tailwindcss, dart-ls which send CompletionItemKind: Color completions, tend to include the hex color at the end of documentation.
This is useful to be able to make colored completion boxes next to each item, as what happens in the Helix editor:
But, it is hard to rely on each language server to properly send the response to contain the hex color at the end of the documentation
This is why it would be useful to make it a part of the LSP spec.
The text was updated successfully, but these errors were encountered:
nik-rev
changed the title
Standardise CompletionItemKind: Color documentation format to always include the hex color at the end
Proposal: Standardise CompletionItemKind: Color documentation format to always include the hex color at the end
Jan 22, 2025
Language servers such as
vscode-css
,tailwindcss
,dart-ls
which sendCompletionItemKind: Color
completions, tend to include the hex color at the end of documentation.This is useful to be able to make colored completion boxes next to each item, as what happens in the Helix editor:
But, it is hard to rely on each language server to properly send the response to contain the hex color at the end of the documentation
This is why it would be useful to make it a part of the LSP spec.
The text was updated successfully, but these errors were encountered: