Microsoft/TypeScript
Condition aliasing doesn't capture optional chain expressions
開放
#49,075 建立於 2022年5月11日
BugDomain: check: Control FlowHelp Wanted
倉庫指標
- 星標
- (108,860 顆星)
- PR 合併指標
- (PR 指標待抓取)
描述
Bug Report
🔎 Search Terms
undefined optional chain aliased condition narrowing
🕗 Version & Regression Information
- This is the behavior in every version I tried (from 4.4 onward, when we added aliased conditions).
⏯ Playground Link
💻 Code
interface Foo {
getValues(): number[];
}
declare const foo: Foo | undefined;
const vals = foo?.getValues();
if (vals) {
foo; // Foo | undefined
}
const vals2 = foo && foo.getValues();
if (vals2) {
foo; // Foo
}
if (foo?.getValues()) {
foo; // Foo
}
🙁 Actual behavior
foo is potentially undefined in the first if block. The assignments fail.
(Added assignments so there's some feedback now that the playground's //^? doesn't work pre-4.6.)
🙂 Expected behavior
foo is narrowed to Foo in the first if block, matching the narrowing in the other if blocks.