The VSCode implementation exposes mix_task name(because it relies on the mix tool) but I decided to go with the elixir name.
It might be a bit confusing(I can add a note in the README regarding that) but at the same time, it kind of makes the naming more consistent.
But I am happy to change it to mix_task
Using elixer is fine by me. I'll probably add support for alternative type names so vscode configurations would still work with the mix_task type would still work.
This PR adds Elixir support
The implementation is based on https://github.com/elixir-lsp/vscode-elixir-ls which adds some wrappers on top of https://github.com/elixir-lsp/elixir-ls
The VSCode implementation exposes
mix_task
name(because it relies on themix
tool) but I decided to go with theelixir
name. It might be a bit confusing(I can add a note in the README regarding that) but at the same time, it kind of makes the naming more consistent. But I am happy to change it tomix_task