summaryrefslogtreecommitdiff
path: root/start/lspconfig-0.1.8/lua/lspconfig/server_configurations/elmls.lua
blob: f42449d47c6f89d4bb19fadad01fc81942302f70 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
local util = require 'lspconfig.util'
local lsp = vim.lsp
local api = vim.api

local default_capabilities = lsp.protocol.make_client_capabilities()
default_capabilities.offsetEncoding = { 'utf-8', 'utf-16' }
local elm_root_pattern = util.root_pattern 'elm.json'

return {
  default_config = {
    cmd = { 'elm-language-server' },
    -- 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 = {
      elmReviewDiagnostics = 'off', -- 'off' | 'warning' | 'error'
      skipInstallPackageConfirmation = false,
      disableElmLSDiagnostics = false,
      onlyUpdateDiagnosticsOnSave = false,
    },
  },
  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")]],
    },
  },
}