diff options
| author | Marcus Caisey <marcus@teckna.com> | 2026-05-13 17:53:27 +0100 |
|---|---|---|
| committer | Marcus Caisey <marcus@teckna.com> | 2026-05-21 18:22:13 +0100 |
| commit | d6d03716cf8628de7d9a261e1caeb5cefeb74774 (patch) | |
| tree | c2e3b377108738f04b391c922c65e5cf79d7f9d8 /runtime/syntax/cpp.vim | |
| parent | ce7df01391be8df721c5de1c57d4b254a7792524 (diff) | |
| download | rneovim-d6d03716cf8628de7d9a261e1caeb5cefeb74774.tar.gz rneovim-d6d03716cf8628de7d9a261e1caeb5cefeb74774.tar.bz2 rneovim-d6d03716cf8628de7d9a261e1caeb5cefeb74774.zip | |
fix(lsp): show detail in popup when server can't completionItem/resolve
Problem:
`CompletionItem.detail` is only shown in the info popup if the server
supports `completionItem/resolve`.
Solution:
If the server doesn't support `completionItem/resolve`, prepend the
complete item `info` with `CompletionItem.detail` in a fenced codeblock,
same as we do when the server supports `completionItem/resolve`.
To ensure that completion items are displayed in the same way,
regardless of whether the server supports `completionItem/resolve`, i've
extracted out the test logic from the `selecting an item triggers
completionItem/resolve + (snippet) preview` case so that we can run the
same tests against a server which supports `completionItem/resolve` and
one which doesn't. Hopefully this should prevent the two behaviours
diverging again.
Diffstat (limited to 'runtime/syntax/cpp.vim')
0 files changed, 0 insertions, 0 deletions