diff options
author | LW <git@llllvvuu.dev> | 2023-11-12 04:54:27 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-12 04:54:27 -0800 |
commit | 448907f65d6709fa234d8366053e33311a01bdb9 (patch) | |
tree | 17dcb47f3f7481f7ded11e0675309461c7a15973 /runtime/lua/vim/lsp.lua | |
parent | ad3568a70167ceb870931650afb7dcaed88640ec (diff) | |
download | rneovim-448907f65d6709fa234d8366053e33311a01bdb9.tar.gz rneovim-448907f65d6709fa234d8366053e33311a01bdb9.tar.bz2 rneovim-448907f65d6709fa234d8366053e33311a01bdb9.zip |
feat(lsp)!: vim.lsp.inlay_hint.get(), enable(), is_enabled() #25512
refactor!: `vim.lsp.inlay_hint()` -> `vim.lsp.inlay_hint.enable()`
Problem:
The LSP specification allows inlay hints to include tooltips, clickable
label parts, and code actions; but Neovim provides no API to query for
these.
Solution:
Add minimal viable extension point from which plugins can query for
inlay hints in a range, in order to build functionality on top of.
Possible Next Steps
---
- Add `virt_text_idx` field to `vim.fn.getmousepos()` return value, for
usage in mappings of `<LeftMouse>`, `<C-LeftMouse>`, etc
Diffstat (limited to 'runtime/lua/vim/lsp.lua')
-rw-r--r-- | runtime/lua/vim/lsp.lua | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/runtime/lua/vim/lsp.lua b/runtime/lua/vim/lsp.lua index 82a88772bd..261a3aa5de 100644 --- a/runtime/lua/vim/lsp.lua +++ b/runtime/lua/vim/lsp.lua @@ -24,6 +24,7 @@ local lsp = { buf = require('vim.lsp.buf'), diagnostic = require('vim.lsp.diagnostic'), codelens = require('vim.lsp.codelens'), + inlay_hint = require('vim.lsp.inlay_hint'), semantic_tokens = semantic_tokens, util = util, @@ -2439,13 +2440,6 @@ function lsp.with(handler, override_config) end end ---- Enable/disable/toggle inlay hints for a buffer ----@param bufnr (integer) Buffer handle, or 0 for current ----@param enable (boolean|nil) true/false to enable/disable, nil to toggle -function lsp.inlay_hint(bufnr, enable) - return require('vim.lsp.inlay_hint')(bufnr, enable) -end - --- Helper function to use when implementing a handler. --- This will check that all of the keys in the user configuration --- are valid keys and make sense to include for this handler. |