VimPlug/ale
1
0
Fork 0
mirror of https://github.com/dense-analysis/ale.git synced 2026-04-25 08:54:00 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
4,650 Commits 29 Branches 39 Tags
6ba798d2e773905feb609bf530e681acbdaea22c
Commit Graph

2 Commits

Author SHA1 Message Date
coriocactus 6ba798d2e7 fix expert lsp stdio and register capability (#5113)
CI / build_image (push) Has been cancelled
Details
CI / test_ale (--linters-only) (push) Has been cancelled
Details
CI / test_ale (--lua-only) (push) Has been cancelled
Details
CI / test_ale (--neovim-07-only) (push) Has been cancelled
Details
CI / test_ale (--neovim-08-only) (push) Has been cancelled
Details
CI / test_ale (--vim-80-only) (push) Has been cancelled
Details
CI / test_ale (--vim-90-only) (push) Has been cancelled
Details 
* 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
 2026-04-10 23:20:22 +09:00
pmonson711 962a932ed4 add support for expert (#5036) 
* add support for expert

* Refactor elixir expert linter from feedback

- Simplify configuration by removing executable lookup logic
- Update documentation to reflect current configuration options
- Rename test file and update assertions for the new configuration

* default to expert for the lsp

The install instructions included something I missed. It includes a
global install, where the default executable is just `expert`. I'll
default to that and review if I should should add a configuration for a
global config.

---------

Co-authored-by: Your Name <pmonson711@nfiindustries.com>
 2025-11-22 21:15:52 +09:00