hermes - 💡(How to fix) Fix [Feature]: Use `expert` instead of `elixir-ls` as an Elixir LSP

Problem or Use Case

Currently, elixir-ls doesn't work as intended - it just returns empty diagnostics

Proposed Solution

I decided not to look into it much as it's quite complicated and would require patching the source. Instead, as I'm using NixOS, I just symlinked expert as elixir-ls into Hermes's container with some obvious patches to make it work (e.g. adding --stdio):

    {
      name = "elixir-ls";
      pkg = pkgs.writeShellScriptBin "elixir-ls" ''
        exec ${expert-lsp.packages.${pkgs.system}.default}/bin/expert --stdio "$@"
      '';
    }

I think it'd be nice if we just replaced elixir-ls with expert altogether so Elixir users won't need to jump through hoops

Alternatives Considered

Just fixing elixir-ls. But I personally don't think this is a viable solution, as expert is stable now and is considered to be "the official Elixir LSP". While elixir-ls does have some features that one might deem useful, they aren't used by Hermes at all, so it'll be a drop-in replacement.

Another alternative would be both fixing elixir-ls (which again I'm unsure why it doesn't work) and adding expert as an alternative option. This is a viable solution, but it might be slightly confusing.

Feature Type

Configuration option

Scope

Small (single file, < 50 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)