microsoft / microsoft/TypeScript
Mapped Type `[Lhs of Rhs]` Syntax for Array and Tuple 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
Suggestion
🔍 Search Terms
mapped type, of, array, tuple
✅ Viability Checklist
My suggestion meets these guidelines:
- 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 feature would agree with the rest of TypeScript's Design Goals.
⭐ Suggestion
A new [Lhs of Rhs] syntax in mapped type to map over values of array and tuple types:
type ResultType = {
[V of SourceType]: DoSomethingWith<V>
}
Rhs does not need to be a type parameter.
Rhs must extend readonly unknown[] or a type error is raised.
📃 Motivating Example
type Foo = ['hello', 'world']
type Bar = {
[V of Foo]: V[]
}
// Bar = ['hello'[], 'world'[]]
💻 Use Cases
Currently, to do the same as in motivating example, one might intuitively write:
type Bar = {
[K in keyof Foo]: Foo[K][]
}
However this is incorrect and is a mistake that's potentially difficult to spot.
Instead one must either introduce a generic intermediate type:
type Transform<T> = {
[K in keyof T]: T[K][]
}
type Bar = Transform<Foo>
Or use the infer workaround:
type Bar = Foo extends infer T ? {
[K in keyof T]: T[K][]
} : never
Both workarounds are not immediately obvious to inexperienced developers, less ergonomic, and will silently break when Foo is no longer an array or tuple type without putting extra constraints.
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
Comienza comparando los ejemplos propuestos de [Lhs of Rhs] con la solución alternativa existente basada en keyof para mapped types y su comportamiento con arrays y tuplas. Determina después las áreas del compilador y las pruebas que rigen los mapped types y define la sintaxis aceptada, la restricción readonly unknown[], los tipos de tupla resultantes y los diagnósticos para lados derechos no válidos.
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
- Bastante claro
- Aptitud para principiantes
- 25/100