rneovim.git/runtime/lua/vim/lsp/protocol.lua, branch aucmd_textputpost Neovim fork with Rahm's personal hacks. fix(lsp): advertise workspace.didChangeConfiguration capability (#26028) 2023-11-13T18:39:43+00:00 Chris Simon chris@devcycles.io 2023-11-13T18:39:43+00:00 48bcc7b9710d6db619b05254ea87f4087cdd9764 This ensures workspace/didChangeConfiguration notification sent after init is correctly handled 
This ensures workspace/didChangeConfiguration notification sent after init is correctly handled
feat(lsp)!: vim.lsp.inlay_hint.get(), enable(), is_enabled() #25512 2023-11-12T12:54:27+00:00 LW git@llllvvuu.dev 2023-11-12T12:54:27+00:00 448907f65d6709fa234d8366053e33311a01bdb9 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 
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
 refactor(lsp): move completion logic into _completion module 2023-10-21T11:49:05+00:00 Mathias Fussenegger f.mathias@zignar.net 2023-10-21T07:47:24+00:00 1e10310f4cc70cf95a68457c2be9e7459b5bbba6 To reduce cross-chatter between modules and for https://github.com/neovim/neovim/issues/25272 Also preparing for https://github.com/neovim/neovim/issues/25714 
To reduce cross-chatter between modules and for https://github.com/neovim/neovim/issues/25272
Also preparing for https://github.com/neovim/neovim/issues/25714
feat(lsp): add snippet API (#25301) 2023-10-21T06:51:26+00:00 Maria José Solano majosolano99@gmail.com 2023-10-21T06:51:26+00:00 f1775da07fe48da629468bcfcc2a8a6c4c3f40ed 






fix(gen_lsp.lua): no notifications in lsp.Methods #24530
2023-08-03T09:52:21+00:00

Raphael
glephunter@gmail.com

2023-08-03T09:52:21+00:00

214b125132778c5d51d4d7e673d31a9be835e150

Problem:
- Notifications are missing from `lsp.Methods`.
- Need a way to represent `$/` prefixed methods.

Solution:
- Generate notifications.
- Use "dollar_" prefix for `$/` methods.




Problem:
- Notifications are missing from `lsp.Methods`.
- Need a way to represent `$/` prefixed methods.

Solution:
- Generate notifications.
- Use "dollar_" prefix for `$/` methods.






feat(gen_lsp.lua): sort by name, handle failure #24504
2023-08-01T14:13:22+00:00

Justin M. Keyes
justinkz@gmail.com

2023-08-01T13:52:53+00:00

f41496ce74fb30c18bb9a03027a172800b269643












feat(gen_lsp.lua): protocol.Methods #24504
2023-08-01T14:05:06+00:00

mathew
glepnir@neovim.pro

2023-07-28T07:24:18+00:00

da09f9b551badfb3fd363589009168560ae607f6












fix(lsp): announce publishDiagnostics.dataSupport (#24442)
2023-07-24T17:26:17+00:00

Bruce Weirdan
weirdan@gmail.com

2023-07-24T17:26:17+00:00

966eb8e0b3be1b409e491d5cf1e32e82e806a134

Neovim already passed `data` element from published diagnostic to code action, but failed to announce it in client capabilities.

Here is the test that shows that `data` element is returned by `vim.lsp.diagnostic.get_line_diagnostics()`:

https://github.com/neovim/neovim/blob/f56c1848091bb64c63b5bc25ec74bcbd2f52bdde/test/functional/plugin/lsp/diagnostic_spec.lua#L103-L115

and then `get_line_diagnostics()` is used to construct the context for code action request:

https://github.com/neovim/neovim/blob/f56c1848091bb64c63b5bc25ec74bcbd2f52bdde/runtime/lua/vim/lsp/buf.lua#L742




Neovim already passed `data` element from published diagnostic to code action, but failed to announce it in client capabilities.

Here is the test that shows that `data` element is returned by `vim.lsp.diagnostic.get_line_diagnostics()`:

https://github.com/neovim/neovim/blob/f56c1848091bb64c63b5bc25ec74bcbd2f52bdde/test/functional/plugin/lsp/diagnostic_spec.lua#L103-L115

and then `get_line_diagnostics()` is used to construct the context for code action request:

https://github.com/neovim/neovim/blob/f56c1848091bb64c63b5bc25ec74bcbd2f52bdde/runtime/lua/vim/lsp/buf.lua#L742






feat(lsp): implement textDocument/diagnostic (#24128)
2023-07-20T07:03:48+00:00

Chris AtLee
chris@atlee.ca

2023-07-20T07:03:48+00:00

63b3408551561127f7845470eb51404bcd6f547b












fix(lsp): remove unknown LSP protocol property (#24345)
2023-07-14T05:36:10+00:00

Techatrix
19954306+Techatrix@users.noreply.github.com

2023-07-14T05:36:10+00:00

2ecba65b4ba741618ecbfd2a50a939987078bc98

'hierarchicalWorkspaceSymbolSupport' is not part of the LSP Specification




'hierarchicalWorkspaceSymbolSupport' is not part of the LSP Specification