Microsoft/TypeScript
GitHub ã§èŠãDiscriminated union with 11+ items does not handle nullability same as union with <10 items
Open
#62,511 opened on 2025幎9æ29æ¥
BugDomain: check: Big UnionsHelp Wanted
Repository metrics
- Stars
- Â (48,455 stars)
- PR merge metrics
-  (å¹³åããŒãž 6d 17h) (30d ã§ 9 merged PRs)
説æ
ð Search Terms
10 11 union undefined type Nullability narrowing is inconsistent between type discriminated unions of <=10 items and >10 items
ð Version & Regression Information
- This changed between versions 4.2.3 and 4.3.5 (before it would complain about undefined in both cases)
⯠Playground Link
ð» Code
// Union with 11+ items does not handle nullability same as union with <10 items
declare let a3: { type: "1" } | { type: "2" } | undefined;
if(a3!.type === "1"){
// 'a3' is possibly 'undefined'.(18048)
console.log(a3.type);
}
declare let a10: { type: "1" } | { type: "2" } | { type: "3" } | { type: "4" } | { type: "5" } | { type: "6" } | { type: "7" } | { type: "8" } | { type: "9" } | { type: "10" } | undefined;
if(a10!.type === "1"){
// No error (better behavior?)
console.log(a10.type);
}
ð Actual behavior
Complains about undefined for unions with >10 members, but not for unions <11
ð Expected behavior
It seems like it should not error in either case - the code inside the if can only execute if the a3 variable is not undefined
Additional information about the issue
Relevant function in checker.ts: getKeyPropertyName(). That is where the 10 magic value comes from.