microsoft / microsoft/TypeScript
[ID-Prep] Preserve type nodes from function expressions in initialisers
Abierto
Nadie ha tomado este issue todavía.
Committed
Suggestion
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.4k
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 117
Descripción
🔍 Search Terms
declaration emit preserve types from functions
✅ 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
Preserve types from function expressions in initializers when emitting declarations.
📃 Motivating Example
// index.ts
type P = {} & { foo: boolean };
export let fn = (p: P, p2:typeof p) => {}
// index-current.d.ts
type P = {} & { foo: boolean };
export declare let fn: (p: P, p2: {
foo: boolean;
}) => void;
export {};
// index-proposed.d.ts
type P = {} & { foo: boolean };
export declare let fn: (p: P, p2: typeof p2) => void;
export {};
💻 Use Cases
- What do you want to use this for?
This would improvement would can bring us closer to external declaration emitters being a reality. - What shortcomings exist with current approaches?
An external tool can extract the type from the function expression, but then they would have different declarations. It would be great if, where possible, typescript would also preserve types as written. - What workarounds are you using in the meantime?
We could force users to always specify the type even when it's obvious from the function expression, but this makes for very frustrating DX
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
No se nombran archivos fuente, pruebas ni puntos de entrada. Reproduce el ejemplo que motiva el problema e inspecciona el comportamiento de TypeScript al emitir declaraciones; la tarea estará terminada cuando los tipos de los inicializadores de expresiones de función se conserven tal como están escritos en la declaración emitida, sin cambiar la salida de JavaScript.
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
- 35/100