fix expert lsp stdio and register capability (#5113)
CI / build_image (push) Has been cancelled
CI / test_ale (--linters-only) (push) Has been cancelled
CI / test_ale (--lua-only) (push) Has been cancelled
CI / test_ale (--neovim-07-only) (push) Has been cancelled
CI / test_ale (--neovim-08-only) (push) Has been cancelled
CI / test_ale (--vim-80-only) (push) Has been cancelled
CI / test_ale (--vim-90-only) (push) Has been cancelled

* pass --stdio flag to expert lsp server

expert requires --stdio to use stdio transport but the linter
definition launched it without the flag, so the server never
entered lsp mode

* handle client/registerCapability requests from lsp servers

some lsp servers like expert send a client/registerCapability
request after initialization to dynamically register capabilities,
if ale does not respond the server blocks and never processes
further messages like textDocument/didOpen
This commit is contained in:
coriocactus
2026-04-10 15:20:22 +01:00
committed by GitHub
parent b1b027d5e6
commit 6ba798d2e7
4 changed files with 29 additions and 3 deletions
+1 -1
View File
@@ -7,6 +7,6 @@ call ale#linter#Define('elixir', {
\ 'name': 'expert',
\ 'lsp': 'stdio',
\ 'executable': {b -> ale#Var(b, 'elixir_expert_executable')},
\ 'command': '%e',
\ 'command': '%e --stdio',
\ 'project_root': function('ale#handlers#elixir#FindMixUmbrellaRoot'),
\})