microsoft / microsoft/TypeScript
Nullish coalescing operator but for conditional types
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.4k
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 117
Descripción
🔍 Search Terms
nullish coalescing operator
conditional types
✅ 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
Add syntactic sugar to allow this:
type T = A extends B ?? C
to be shorthand of:
type T = A extends B ? A : C
📃 Motivating Example
When working with large complicated types, it is often that you need to check that a type extends another type before passing it as a type argument to another type.
For example, ensuring it is an array before passing it to something that requires it to be an array:
type Foo<T> = Bar<
Some<Really<Deep<Complex<Type<Utility<T>>>>>> extends readonly unknown[]
? Some<Really<Deep<Complex<Type<Utility<T>>>>>>
: never
>;
type Bar<T extends readonly unknown[]> = ...;
The more complex the type you need to check, the more you need to repeat yourself to pass the same type in again.
This proposal aims to address that.
type Foo<T> = Bar<
Some<Really<Deep<Complex<Type<Utility<T>>>>>> extends readonly unknown[] ?? never
>;
💻 Use Cases
- What do you want to use this for?
Making my type code more readable and easier to maintain.
- What shortcomings exist with current approaches?
The need to repeat yourself. Updates to the type need to be make in two places.
- What workarounds are you using in the meantime?
The long-form syntax.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
El issue no menciona archivos de implementación ni pruebas. Empieza trazando cómo se analizan y comprueban los tipos condicionales, y después determina los cambios de sintaxis y del sistema de tipos necesarios para que A extends B ?? C se comporte como A extends B ? A : C; se considera terminado cuando se acepta la forma abreviada y presenta el comportamiento de tipos equivalente indicado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- typescript
- Área
- compilers
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 30/100