You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Editor Plugin/LSP Client name and version: ElixirLS (v0.21.3)
Current behavior
Hi all, I searched through for similar issues and couldn't find one so apologies if I missed it.
When running the phx.gen.auth Phoenix generator, in the router.ex file I noticed that I wasn't able to jump to definition for the PentoWeb.UserAuth module in the code seen below:
However, when I omitted the module name and changed it to just UserAuth, ElixirLS was able to provide a hyperlink that points me correctly to the module definition.
This seems to be confined to identifiers in tuples because in other parts of the code (see below), it works just fine.
Expected behavior
ElixirLS should know how to jump to definition if the module name is explicitly provided on an identifier inside a tuple.
The text was updated successfully, but these errors were encountered:
lukaszsamson
changed the title
"Go to definition" not working for identifier inside tuple with explicit parent module name
[Feature request][Phoenix] "Go to definition" not working for identifier inside tuple with explicit parent module name
Jul 8, 2024
Environment
Current behavior
Hi all, I searched through for similar issues and couldn't find one so apologies if I missed it.
When running the
phx.gen.auth
Phoenix generator, in therouter.ex
file I noticed that I wasn't able to jump to definition for thePentoWeb.UserAuth
module in the code seen below:However, when I omitted the module name and changed it to just
UserAuth
, ElixirLS was able to provide a hyperlink that points me correctly to the module definition.This seems to be confined to identifiers in tuples because in other parts of the code (see below), it works just fine.
Expected behavior
ElixirLS should know how to jump to definition if the module name is explicitly provided on an identifier inside a tuple.
The text was updated successfully, but these errors were encountered: