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
When using aliases or importing all functions of a module, it's useful to know the origin of the function right where you are using it. This is an example of how it works on Elixir language server:
Current Behavior
Currently we only get the function docs. But see how there is nothing here that points to Url.Builder :
Context
When debugging a piece of code it's pretty useful to not leave the scope of the function I'm trying to understand. Currently I have to backtrack the origin of multiple functions and hold it all in my head while I understand the thing I was actually focusing on.
The text was updated successfully, but these errors were encountered:
I had thought about this too!
Since in Elm and other languages with similar module system, we create "namespaces" using modules and expose similarly-named functions from them. For that we have many functions with the same name from multiple modules. This feature definitely helps identifying therir origins.
Expected Behavior
When using aliases or importing all functions of a module, it's useful to know the origin of the function right where you are using it. This is an example of how it works on Elixir language server:
Current Behavior
Currently we only get the function docs. But see how there is nothing here that points to
Url.Builder
:Context
When debugging a piece of code it's pretty useful to not leave the scope of the function I'm trying to understand. Currently I have to backtrack the origin of multiple functions and hold it all in my head while I understand the thing I was actually focusing on.
The text was updated successfully, but these errors were encountered: