Open augustdolan opened 1 month ago
I figured out how to pull up debug logs and interestingly it seems I'm getting the communication for textDocument/completion
from my LSP, but perhaps the completion is not resulting in anything for some reason:
[DEBUG][2024-05-23 10:06:45] .../vim/lsp/rpc.lua:286 "rpc.send" { id = 2, jsonrpc = "2.0", method = "textDocument/completion", params = { context = { triggerKind = 1 }, position = { character = 3, line = 38 }, textDocument = { uri = "my-path" } }}
[DEBUG][2024-05-23 10:06:45] .../vim/lsp/rpc.lua:408 "rpc.receive" { id = 9, jsonrpc = "2.0", result = { data = {} }}
Perhaps that means this is an LSP issue and not a LuaSnip issue?
Hey all,
The snippet ecosystem is tightly coupled, so please let me know if you believe I should open this issue elsewhere. Below I provide my two relevant files. I will say that using the
kickstarter.nvim
and providingtsserver = { capabilities = capabilities }
to set enable the completion protocol does not result in any changes from my config. Nor does it result in changes if I using the lspconfig.tsserver.setup syntax. I also followed another individuals configuration to see if it would help me, and although they show snippet expansion for TS, I still do not receive it.The issue is that while I receive, say, a function name I defined in typescript in my autocomplete, selecting that function does not expand the snippet, it only completes the word.
In lua, defined functions are able to expand into snippets properly.
I would appreciate any guidance. I've been attempting to debug for hours now, and there seems to be little out there in terms of other people experiencing this issue.
lsp config:
autocomplete config: