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
Hovering over alias on one of the bottom lines will show a popup with a "References" section that links to the other bottom one.
Expected behavior
It'd be great if there was also a "Definitions" section in the popup that linked to the alias on the first line. Ideally, it would be a definition for the one file. (i.e. alias in other files would not find it.)
If I hadn't given thing an alias, uses of thing would be linked to the thing definition in module.py, but there isn't any definition for alias apart from the import as.
Actual behavior
Understandably, there is no Definitions section currently in the popup.
The text was updated successfully, but these errors were encountered:
The question here is how to distinguish module imports from functions etc.
thing could be anything - a module, function, variable. Don't think it's useful to just scope it entity.name without being able to properly link it with references.
Hovering over
alias
on one of the bottom lines will show a popup with a "References" section that links to the other bottom one.Expected behavior
It'd be great if there was also a "Definitions" section in the popup that linked to the
alias
on the first line. Ideally, it would be a definition for the one file. (i.e.alias
in other files would not find it.)If I hadn't given
thing
an alias, uses ofthing
would be linked to thething
definition inmodule.py
, but there isn't any definition foralias
apart from theimport as
.Actual behavior
Understandably, there is no Definitions section currently in the popup.
The text was updated successfully, but these errors were encountered: