[isolatedDeclarations][5.5] Type annotations needed for literals containing enum values

🔍 Search Terms

enum, isolated declarations

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Enum values seem trivially inferrable if the enum is defined in the lexical scope, so isolated declarations shouldn't report them as errors.

📃 Motivating Example

export enum Foo {
  A = 1,
  B = 2,
}

export const x = Foo.A as const;
             ~
export const y = [Foo.A] as const;
                  ~~~~~

Playground: https://tsplay.dev/w68Prm

💻 Use Cases

Self-apparent

Beginne mit dem im TypeScript Playground-Beispiel des Issues gezeigten Verhalten von isolatedDeclarations und untersuche die isolated-declaration-Diagnosen und Type-Checking-Einstiegspunkte des Compilers. Bestätige, wie Enum-Werte für exportierte Literale und Tupel-Elemente inferiert werden; als erledigt gilt, wenn die gezeigten Foo.A-Beispiele keine Fehler mehr melden und eine gültige Declaration-Ausgabe erhalten bleibt.