Inconsistent object literal key completion for enum keys

[sadan4]

🔎 Search Terms

enum AND object AND keys

🕗 Version & Regression Information

I tried various versions up to nightly (v6.0.0-dev.20251030) with no results

⏯ Playground Link

https://www.typescriptlang.org/play/?ts=6.0.0-dev.20251030#code/KYOwrgtgBAsgngUXNA3gKCpqAxA8rgGgywCEBBAJSIF800BjAexAGcAXKAM0cYC4oKwJgCcAJgB54SSASjthASxABzAHxQAvFHRYoAej1Q2wuEcZQmEAA4AbYG2BQA1sDgsoSowAsF7xgCMAKyE2YkwDKGAAD2ArEOBRKABtKWQAOjxcAF1ZFMR08gossP1DAEN6NjAymygAIgAGOtk6gEY6tGogA

💻 Code

enum MyEnum {
    FOO,
    BAR,
}

const foo: Record<MyEnum, string> = {
    // try to complete keys in this object
    // expected [MyEnum.FOO], [MyEnum.BAR]
    // actual "0", "1"
}

🙁 Actual behavior

"0" and "1" are suggested as completions

🙂 Expected behavior

[MyEnum.FOO] and [MyEnum.BAR] are suggested as completions

Additional information about the issue

using the quick fix Add Missing Properties uses the correct, expected behaviour

[snarbles2]

If you type the open bracket and then hit alt+space or "M", you get a completion list with MyEnum at the top. Sans brackets, "0" and "1" are the suggestions. This seems to make sense—it provides whichever options are syntactically valid.

[sadan4]

If you type the open bracket and then hit alt+space or "M", you get a completion list with MyEnum at the top. Sans brackets, "0" and "1" are the suggestions.

To do this you have to type [, press CTRL+space or M to show completions, complete MyEnum, press . to start completions for members of MyEnum, and only then can you complete your desired key. Even after you complete your desired key, your cursor will still be within the brackets, so you need to exit the brackets as well. The ability to just press CTRL+space then being able to complete your desired key and start typing right away is considerably more convenient than that.

[snarbles2]

Well, I was responding to this issue as a bug report. You normally get a list of relevant identifiers. It seems odd to expect complex bracketed, dotted completions like [SomeEnum.ValueName]. I certainly wouldn't consider it a bug. As a feature suggestion, yes, I agree. It would be pleasant to have [SomeEnum.ValueName] among the top of the suggestions.

[sadan4]

Well, I was responding to this issue as a bug report. You normally get a list of relevant identifiers. It seems odd to expect complex bracketed, dotted completions like [SomeEnum.ValueName]. I certainly wouldn't consider it a bug. As a feature suggestion, yes, I agree. It would be pleasant to have [SomeEnum.ValueName] among the top of the suggestions.

I should have opened a suggestion instead, My bad.