bug: Incorrect Typescript completion with computed property name

[NikolasKomonen]

When doing completions where my interface uses computed property names, the completion result does not
show the correct completion items.

Test Code

const MyKeys = {
    KEY_1: 'key_1',
    KEY_2: 'key_2',
    KEY_3: 'key_3',
} as const

const MyKeys2 = {
    KEY_1: 'key_1',
    KEY_2: 'key_2',
    KEY_3: 'key_3',
} as const

interface MyInterface {
    [MyKeys2.KEY_1]: string,
    [MyKeys.KEY_2]: string,
    [MyKeys.KEY_3]: string
}

const myObj: MyInterface = {
    key_1: 'value_1',
    key_2: 'value_2',
    key_3: 'value_3',
}

myObj.

Current Incorrect Completion Result

Expected

Instead I would expect 3 completion results:

• key_1
• key_2
• key_3

Additional Findings

It looks like the first use of a specific const (MyKeys or MyKeys2) in the interface MyInterface is replaced with the wrong value, but all subsequent references (key_3) show up correctly

Version Info

Version: 1.77.3 (Universal)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:19:37.325Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: Yes

[RyanCavanaugh]

This is correct behavior. If you complete the entry, you'll get an indexed access snippet:

myObj[MyKeys2.

which corresponds to the declaration form you used to write the object in the first place

[NikolasKomonen]

@RyanCavanaugh thanks for the quick response. Makes sense to me that that is the intended use.

I'm wondering why keys_3 is shown in the example image? Would it make sense to only show the completion results MyKeys and MyKeys2 then?

[RyanCavanaugh]

Good point - I have no idea why it's mixing and matching there. Seems off.