Incorrect hover/definition for compound string key #4719
R-O-C-K-E-T
started this conversation in
Enhancement
Replies: 2 comments
-
@rchiodo or @debonte, please transfer this to the pylance-relase project since it's related to a language server feature. I don't know if this is worth addressing since it's such an edge case and the workaround is obvious — replace the compound key strings with a single string literal. I'll leave it to the pylance team to decide whether to address this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Moving this issue to discussion as an enhancement request for comments and upvotes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
If a compound string (
'prefix' 'suffix'
) is used as a key when constructing aTypedDict
expression where the either the first string or last string section is also a valid key into theTypedDict
, then the info/definition when hovering over those segments is incorrect.Expected behaviour
Either the whole compound string is highlighted and the correct type info for the whole key is shown or no type info should be shown for compound string keys.
Steps
Beta Was this translation helpful? Give feedback.
All reactions