marc/ale
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
ale/test/command_callback/test_elixir_ls_command_callbacks.vader

35 lines
1.1 KiB
Text
Raw Normal View History

Add elixir-ls language server support ElixirLS (https://github.com/JakeBecker/elixir-ls) is an LSP server for Elixir. It's distributed as a release package that can be downloaded from https://github.com/JakeBecker/elixir-ls/releases or built locally. The easiest way to start it is via Unix- and Win32-specific helper scripts, so that's the basis of this command integration. Alternatively, we could implement the contents of those platform-specific scripts in the linter's command callback in a language-neutral way, but there isn't any benefit to doing that aside from eliminating the platform check, and that could prove to be too tight of a coupling going forward.
2018-09-28 18:42:50 +00:00
Before:
call ale#assert#SetUpLinterTest('elixir', 'elixir_ls')
After:
call ale#assert#TearDownLinterTest()
#2132 - Implement feature tests with ale#Has
2019-04-07 14:34:39 +00:00
Execute(should set correct defaults):
if has('win32')
AssertLinter 'elixir-ls\language_server.bat', 'elixir-ls\language_server.bat'
else
AssertLinter 'elixir-ls/language_server.sh', 'elixir-ls/language_server.sh'
endif
Add elixir-ls language server support ElixirLS (https://github.com/JakeBecker/elixir-ls) is an LSP server for Elixir. It's distributed as a release package that can be downloaded from https://github.com/JakeBecker/elixir-ls/releases or built locally. The easiest way to start it is via Unix- and Win32-specific helper scripts, so that's the basis of this command integration. Alternatively, we could implement the contents of those platform-specific scripts in the linter's command callback in a language-neutral way, but there isn't any benefit to doing that aside from eliminating the platform check, and that could prove to be too tight of a coupling going forward.
2018-09-28 18:42:50 +00:00
Execute(should configure elixir-ls release location):
let b:ale_elixir_elixir_ls_release = 'boo'
#2132 - Implement feature tests with ale#Has
2019-04-07 14:34:39 +00:00
if has('win32')
AssertLinter 'boo\language_server.bat', 'boo\language_server.bat'
else
AssertLinter 'boo/language_server.sh', 'boo/language_server.sh'
endif
Add elixir-ls language server support ElixirLS (https://github.com/JakeBecker/elixir-ls) is an LSP server for Elixir. It's distributed as a release package that can be downloaded from https://github.com/JakeBecker/elixir-ls/releases or built locally. The easiest way to start it is via Unix- and Win32-specific helper scripts, so that's the basis of this command integration. Alternatively, we could implement the contents of those platform-specific scripts in the linter's command callback in a language-neutral way, but there isn't any benefit to doing that aside from eliminating the platform check, and that could prove to be too tight of a coupling going forward.
2018-09-28 18:42:50 +00:00
Execute(should set correct LSP values):
elixir-ls now recognizes umbrella projects Previously, elixir-ls would treat each sub-project within an umbrella as standalone, which isn't desirable from a language server perspective. Added ale#handlers#elixir#FindMixUmbrellaRoot, which locates the current project's root and then continues searching upwards for a potential umbrella project root. This literally looks just two levels up to keep things simple while keeping in line with Elixir project conventions. Use this new function to determine elixir-ls's LSP project root.
2018-11-01 20:35:18 +00:00
call ale#test#SetFilename('elixir_paths/umbrella_project/apps/app1/lib/app.ex')
Add elixir-ls language server support ElixirLS (https://github.com/JakeBecker/elixir-ls) is an LSP server for Elixir. It's distributed as a release package that can be downloaded from https://github.com/JakeBecker/elixir-ls/releases or built locally. The easiest way to start it is via Unix- and Win32-specific helper scripts, so that's the basis of this command integration. Alternatively, we could implement the contents of those platform-specific scripts in the linter's command callback in a language-neutral way, but there isn't any benefit to doing that aside from eliminating the platform check, and that could prove to be too tight of a coupling going forward.
2018-09-28 18:42:50 +00:00
AssertLSPLanguage 'elixir'
AssertLSPOptions {}
Add a `lsp_config_callback` linter option This is the callback-based variant of the existing `lsp_config` linter option. It serves the same purpose but can be used when more complicated processing is needed. `lsp_config` and `lsp_config_callback` are mutually exclusive options; if both an given, a linter preprocessing error will be raised. The runtime logic has been wrapped in `ale#lsp_linter#GetConfig` for convenience, similar to `ale#lsp_linter#GetOptions`. This also adds documentation and an `AssertLSPConfig` test function for completeness.
2018-10-30 15:54:40 +00:00
AssertLSPConfig {}
elixir-ls now recognizes umbrella projects Previously, elixir-ls would treat each sub-project within an umbrella as standalone, which isn't desirable from a language server perspective. Added ale#handlers#elixir#FindMixUmbrellaRoot, which locates the current project's root and then continues searching upwards for a potential umbrella project root. This literally looks just two levels up to keep things simple while keeping in line with Elixir project conventions. Use this new function to determine elixir-ls's LSP project root.
2018-11-01 20:35:18 +00:00
AssertLSPProject ale#path#Simplify(g:dir . '/elixir_paths/umbrella_project')
Add configuration dictionary support to elixir-ls This adds generic configuration dictionary support to the elixir-ls linter. This is useful for disabling its built-in Dialyzer support, for example, which can improve startup time. The configuration dictionary is a little verbose. I considered reducing the user configuration to only the nested settings dictionary (and having the linter implementation wrap it in the top-level `elixirLS` dictionary), but leaving it fully configurable simplifies the code and removes any assumptions about current or future ElixirLS behavior.
2018-10-31 17:24:03 +00:00
Execute(should accept configuration settings):
AssertLSPConfig {}
let b:ale_elixir_elixir_ls_config = {'elixirLS': {'dialyzerEnabled': v:false}}
AssertLSPConfig {'elixirLS': {'dialyzerEnabled': v:false}}
Reference in a new issue Copy permalink