Jason Axelson

Is there a chance for this to be re-visited? Or is there any way to work around this limitation from a language server implementation side?

Hi, thanks for the request. Indeed ElixirLS does not currently support refactoring/renaming, but if someone were to tackle it we'd be glad to help get it merged. (I renamed the...

@garrettmichaelgeorge yes, you are on the right track. https://github.com/elixir-lsp/elixir-ls/pull/521 is finishing up the implementation of ManipulatePipes which is the only thing that would fall under refactoring at this point. In...

Hi all, if you'd like this to be built please just leave a :+1: on the issue itself. Comments asking for this to be implemented are not helpful and end...

> Why not just distribute the sources? This is an interesting idea that I hadn't considered before! Especially because there are no nifs (which would make compilation more difficult) >...

I've updated the issue description with goals and requirements, are there any that seem incorrect or that I missed?

@lukaszsamson I wonder if you have time to take a look at #136 and if you have any thoughts. I'm starting to think that we may need to take an...

erlang_ls is moving to at least 2 nodes for similar reasons as us: https://github.com/erlang-ls/erlang_ls/pull/670 once that PR is merged maybe we can learn something from it.

I'm not sure that I like the compromises required for a dependency-based approach. Namely: * As a developer working on a library that doesn't already use ElixirLS I would have...

Hi :wave:, The Language Server Protocol version of that is `textDocument/selectionRange` (docs are at https://microsoft.github.io/language-server-protocol/specification#textDocument_selectionRange, and original discussion was at https://github.com/Microsoft/language-server-protocol/issues/613) We would gladly merge well-written support for selectionRange. I...