do<enter> becomes defoverridable() when creating new functions

[fkumro]

Environment

• Elixir & Erlang versions (elixir --version):

Erlang/OTP 24 [erts-12.0.3] [source] [64-bit] [smp:24:24] [ds:24:24:10] [async-threads:1] [jit]

Elixir 1.12.2 (compiled with Erlang/OTP 24)

• Operating system:

Pop!_OS 21.04

• Editor or IDE name (e.g. Emacs/VSCode):

VSCodium

• Editor Plugin/LSP Client name:

elixir-lsp/vscode-elixir-ls

Troubleshooting

• Restart your editor (which will restart ElixirLS) sometimes fixes issues
• Stop your editor, remove the entire .elixir_ls directory, then restart your editor

Logs

2. Create a new Mix project with mix new empty, then open that project with VS Code and open an Elixir file. Is your issue reproducible on the empty project? If not, please publish a repo on Github that does reproduce it.

Yes, mix new empty will allow you to recreate the issue.

---

Issue

When creating a new function, autocomplete changes do<enter> to defoverridable().

def test do

becomes

def test defoverridable()

[hassanshaikley]

I am not able to recreate this. Unless I literally have an empty file and type in:

do<enter> but I don't see why that is an important behavior?

def x do<enter> behaves correctly.

Is there something I am missing?

[zorn]

I have seen this behavior myself but can not reproduce it right now. Will keep my eye out for what might trigger it.

[axelson]

👋 @fkumro @zorn Can you check that you're on the latest version of ElixirLS? That should be fixed in #593 which was released in 0.8.1. I was just able to test it in my lsp-mode setup:

[fkumro]

👋 @axelson I installed the extension from the Open VSX registry which has the current version at 0.8.0

https://open-vsx.org/extension/elixir-lsp/elixir-ls

[zorn]

My current version is v0.8.1 and as I said, I can not currently recreate it, but have experienced it before. Thanks for the followup. I'm going to jump off the thread unless it pops up again.

[axelson]

@fkumro Okay, it looks like I missed the Open VSX registry when I released 0.8.1. So I just published 0.8.1. Can you upgrade and try again please?

[kinson]

Thanks @axelson, upgrading to v0.8.1 seems to have fixed this issue for me 🎉

[axelson]

@kinson Great! I'm going to go ahead and close it. @fkumro if you're still encountering it let me know and we can re-open it or file a new issue as appropriate. And thanks @hassanshaikley for taking a look at this 👍

[fkumro]

@axelson Updated and the issue is solved, thank you 🙇‍♂️

[axelson]

Great!