Incorrect hover/definition for compound string key

[R-O-C-K-E-T]

Description

If a compound string ('prefix' 'suffix') is used as a key when constructing a TypedDict expression where the either the first string or last string section is also a valid key into the TypedDict, 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

class Test(TypedDict):
    prefix: str
    suffix: str
    prefixsuffix: int

def test_taker(val: Test):
    ...


test: Test = {
    'prefix': 'foo',
    'suffix': 'bar',

    'prefix' 'suffix': 30, # Hovering over 'prefix' or 'suffix' on this line produces incorrect hover text and definition location
}
test_taker({'prefix': 'foo', 'suffix': 'bar', 'prefix' 'suffix': 30})  # Again, hovering over 'prefix' or 'suffix' on this line produces incorrect hover text and definition location

[erictraut]

@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.

[debonte]

Moving this issue to discussion as an enhancement request for comments and upvotes.