2022-03-20 10:22:32 +08:00
local util = require ' lspconfig.util '
2021-10-05 15:13:10 +08:00
local lsp = vim.lsp
local api = vim.api
local bin_name = ' elm-language-server '
2022-03-20 10:22:32 +08:00
local cmd = { bin_name }
if vim.fn . has ' win32 ' == 1 then
cmd = { ' cmd.exe ' , ' /C ' , bin_name }
end
2021-10-05 15:13:10 +08:00
local default_capabilities = lsp.protocol . make_client_capabilities ( )
default_capabilities.offsetEncoding = { ' utf-8 ' , ' utf-16 ' }
local elm_root_pattern = util.root_pattern ' elm.json '
2022-03-20 10:22:32 +08:00
return {
2021-10-05 15:13:10 +08:00
default_config = {
2022-03-20 10:22:32 +08:00
cmd = cmd ,
2021-10-05 15:13:10 +08:00
-- TODO(ashkan) if we comment this out, it will allow elmls to operate on elm.json. It seems like it could do that, but no other editor allows it right now.
filetypes = { ' elm ' } ,
root_dir = function ( fname )
local filetype = api.nvim_buf_get_option ( 0 , ' filetype ' )
if filetype == ' elm ' or ( filetype == ' json ' and fname : match ' elm%.json$ ' ) then
return elm_root_pattern ( fname )
end
end ,
init_options = {
elmAnalyseTrigger = ' change ' ,
} ,
} ,
docs = {
description = [ [
https : // github.com / elm - tooling / elm - language - server # installation
If you don ' t want to use Nvim to install it, then you can use:
` ` ` sh
npm install - g elm elm - test elm - format @ elm - tooling / elm - language - server
` ` `
] ] ,
default_config = {
root_dir = [[root_pattern("elm.json")]] ,
} ,
} ,
}