microsoft / microsoft/TypeScript
Broken assignability and quick info due to erroneously deferring keyof T since #51621
@gabritto ya está trabajando en esto.
Desde el 30/4/2026.
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.3k
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 132
Descripción
Note: This is a refiling of #61728 due to being closed due to being related to quick info display (see #62827).
Version & Regression Information
This changed in PR https://github.com/microsoft/TypeScript/pull/51621
Playground Link
Code:
Poor quick info:
type BasicConditional<T> = keyof T extends any
? true
: false;
type Config = { rejectClose: true };
type Test =
Config extends {}
? {
rejectClose: BasicConditional<Config>;
}
: never;
type RejectClose = Test["rejectClose"];
// ^? keyof Config extends any ? true : false
Broken assignability (found by @Andarist, see https://github.com/microsoft/TypeScript/issues/61728#issuecomment-2891710775)
type BasicConditional<T> = keyof T extends infer R ? R : never;
type Config = { rejectClose: true };
type Test = Config extends {}
? {
rejectClose: BasicConditional<Config>;
}
: never;
const test: Test["rejectClose"] = "rejectClose";
// ^ Type 'string' is not assignable to type 'BasicConditional<Config>'.
const ok: BasicConditional<Config> = "rejectClose"; // No error
Actual behavior
RejectClose's quick info is keyof Config extends any ? true : false which is un-simplified and rather ugly. In addition in the second snippet const test: Test["rejectClose"] = "rejectClose"; fails.
Expected behavior
The quick info should look nice and const test: Test["rejectClose"] = "rejectClose"; should succeed.
See https://github.com/microsoft/TypeScript/pull/61999 for a TS-JS based fix.
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.
Evaluación
Este issue todavía no se ha evaluado.