Better support for .eex files ~E and ~L

[msaraiva]

It seems that the following doesn't work when in a .eex files, ~E or ~L:

• SIgnature
• Docs
• Suggestions for variables defined inside the template

[kenny-evitt]

I'm using ElixirSense via alchemist.vim and I opened an issue on its GitHub project related to this:

• ExDoc and ExDef for functions (or modules) in Embedded Elixir files · Issue #155 · slashmili/alchemist.vim

... but I didn't think it was possible, or feasible, given that the context in which an .eex template file is evaluated doesn't seem to be closely coupled to the file.

But I'm glad I seem to have been wrong!

[msaraiva]

@kenny-evitt regarding ~E and ~L it's totally doable. However, you're right about .eex files. They can be "injected" in any file. Maybe, the best we could do would be to try to find the related view based on the folder/name of the template. But then it would not work when the developer does not follow the convention.

@axelson @lukaszsamson WDYT?

[kenny-evitt]

@msaraiva Maybe, for .eex files, the commands, or new similar commands, could accept both a line and column in the .eex file and a line and column in the relevant 'view' module file. The new commands could be named EexDoc and EexDef.

[axelson]

Yeah for plain ~E and ~L I think that they could be used in multiple contexts so it's impossible to know how it's going to be used. I do like what @kenny-evitt suggested, that seems like a practical compromise which will help in the majority of cases.

[lukaszsamson]

SIgnature and docs definitely work in (h)eex

[lukaszsamson]

Vars in templates tracked in elixir-lsp/vscode-elixir-ls#279