Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom CompletionItemKind outside of LSP definition #590

Open
milanglacier opened this issue Dec 16, 2024 · 0 comments
Open

Allow custom CompletionItemKind outside of LSP definition #590

milanglacier opened this issue Dec 16, 2024 · 0 comments
Labels
feature New feature or request sources Specific source provider or the system as a whole windows Module which displays UI

Comments

@milanglacier
Copy link
Contributor

Feature Description

I want to ask if we can allow customized CompletionItemKind when create backend for blink, aka something like this:

function M:get_completions(context, callback)
    callback {
        items = {
            {
                label = 'hello',
                kind = 'AI',
            },
            {
                label = 'hello world',
                kind = 'AI',
            },
        },
    }
end

Customized item kind outside of the lsp protocol definition are widely used in nvim-cmp, for example, copilot.cmp, codeium.nvim, minuet-ai.nvim are all using customized kind names.

@milanglacier milanglacier added the feature New feature or request label Dec 16, 2024
@Saghen Saghen changed the title Feature Request: allow custom CompletionItemKind outside of LSP definition Allow custom CompletionItemKind outside of LSP definition Dec 16, 2024
@Saghen Saghen added sources Specific source provider or the system as a whole windows Module which displays UI labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request sources Specific source provider or the system as a whole windows Module which displays UI
Projects
None yet
Development

No branches or pull requests

2 participants