Clearer tooltips for nested classes #6057
Replies: 3 comments
-
it is a spec question. we do disambiguate type name within same type such as should we always put full type name somewhere? or full type name everywhere? I think all has its con and pros. |
Beta Was this translation helpful? Give feedback.
-
User setting then perhaps? I can see how even the same user might want it different ways in different workspaces. Or could it be sensitive to a wider context, i.e. show full names only if there is actual ambiguity between classes defined in the codebase? It might be enough if that's done even in a single-file context. |
Beta Was this translation helpful? Give feedback.
-
Transferring to a discussion for upvotes/discussion. |
Beta Was this translation helpful? Give feedback.
-
Not sure if this is a Pylance or a Pyright issue, or even a VS Code issue.
In VS Code, the tooltip for nested classes shows only the base name of the class, which can be unclear:
Hovering over either
a
andb
shows(variable) a: Inner
and(variable) b: Inner
, which obscures the fact that they're actually instances of different classes. It will be helpful if the qualified class name is displayed instead ((variable) a: Foo.Inner
/(variable) b: Bar.Inner
).Beta Was this translation helpful? Give feedback.
All reactions