Completion should suggest enum keys on some conditions

🔍 Search Terms

"enum", "enum keys", "completion"

✅ 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

Suggest enum keys completions without having to spell out the enum identifier.

For example, input CRE should be offered completion State.CREATED.

This completion can be limited to places where the enum type is expected, like a function argument or an object literal.

📃 Motivating Example

enum State {
    CREATED,
    CLOSED,
}

function f(v : State) {}

f(CRE ) // Expect completion on CRE

💻 Use Cases

1. What do you want to use this for? better DX
2. What shortcomings exist with current approaches? Have to first write the enum before enum key completions are offered.
3. What workarounds are you using in the meantime? no

No se nombra ningún archivo, prueba ni punto de entrada. Empieza reproduciendo el ejemplo de completado de enum en el TypeScript language service y sigue cómo se filtran los completados en contextos donde se espera un tipo. Se considera terminado cuando un prefijo como CRE ofrece State.CREATED sin requerir primero el identificador del enum, preservando al mismo tiempo la salida y el comportamiento existentes de JavaScript.