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
Describe the bug
Occasionally when I try to use "Find Usages" on an elixir function in my project I'll get a usages not found message with
the following description
Usages of NameArityInterval(name=def, arityInterval=ArityInterval(2, 2)) Nothing found in 'All Places'
That is, my function doesn't have this name -- it seems be using a general placeholder for searching for the method I'm using.
To Reproduce
Steps to reproduce the behavior:
Load up an elixir project
Right click on a function after loading
In the dropdown, select "Find Usages" -- around 30% of functions (that have actual usages) clicked will arrive with this message and fail to find any usages.
Occasionally, you can get this to work for a given function if you constantly try a bunch of other functions in succession, and come back to the failing function later.
Expected behavior
Find usages window should pop up with the usages or the same message should be displayed but with the actual function name.
Screenshots
Desktop:
OS: macOS
Version 14.7.1
Erlang:
Installer ASDF
Version 26.2 Elixir:
Installer ASDF
Version 1.16.3
Plugin:
Version 20.0.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Occasionally when I try to use "Find Usages" on an elixir function in my project I'll get a usages not found message with
the following description
That is, my function doesn't have this name -- it seems be using a general placeholder for searching for the method I'm using.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Find usages window should pop up with the usages or the same message should be displayed but with the actual function name.
Screenshots
Desktop:
Erlang:
Elixir:
Plugin:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: