microsoft / microsoft/TypeScript
[TypeScript] Mapped Types with Template Literal Keys Do Not Preserve Type Declaration References
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.3k
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 132
Descripción
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.96.4 (Universal)
- OS Version: Darwin arm64 23.6.0 (macOS Sonoma 14.7.2)
- TypeScript Version: 5.7.3
When using Mapped Types with template literal transformations on interface fields, VSCode does not retain the original type reference. This makes it impossible to use “Go to Definition” to navigate from the transformed key back to its original declaration. WebStorm correctly maintains this reference, but VSCode does not.
Steps to Reproduce:
interface Source {
alpha: number;
beta: string;
}
// Transforming interface field names with a suffix
type Transformed<T> = {
[K in keyof T as `${K & string}Suffix`]: () => T[K];
};
type Result = Transformed<Source>;
/*
Expected:
{
alphaSuffix: () => number;
betaSuffix: () => string;
}
*/
const obj: Result = {
alphaSuffix: () => 42,
betaSuffix: () => "hello",
};
// ❌ In VSCode, "Go to Definition" on `alphaSuffix` does not navigate to `alpha` in `Source`
obj.alphaSuffix();
Expected Behavior
- “Go to Definition” on alphaSuffix should navigate to alpha in Source.
- VSCode should retain the reference between transformed keys and their original interface field names.
- This works as expected in WebStorm, where alphaSuffix correctly links back to alpha.
Actual Behavior
- VSCode treats transformed keys as completely new identifiers, losing the connection to their original interface fields.
- “Go to Definition” does not work for mapped types with template literal keys.
- WebStorm successfully tracks the transformation and allows navigation to alpha.
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
Reproduce el ejemplo de mapped types con TypeScript 5.7.3 y prueba Go to Definition desde alphaSuffix hasta Source.alpha. Empieza rastreando la búsqueda de definiciones del servicio de lenguaje de TypeScript para mapped types y claves de template literals; se considera completado cuando la clave transformada navega hasta el campo de su interfaz original y el comportamiento tiene cobertura de regresión.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- typescript
- Área
- developer-experience
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100