microsoft / microsoft/TypeScript
switch-true case-true narrowing not equivalent to default case.
Open
Nobody has claimed this yet.
Domain: check: Control Flow
Help Wanted
Possible Improvement
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
🔎 Search Terms
"switch true" "switch-true" switch true narrowing. Most issues that turned up were from 2023 which I think precedes the release of the switch-true type narrowing feature?
🕗 Version & Regression Information
- This is a gap
⏯ Playground Link
💻 Code
function uhoh(input: string) : "A"|"B"|"C" {
switch (true) {
case /a/.test(input):
return "A";
case /b/.test(input):
return "B";
case true: // <--- default: works fine here
return "C";
}
}
🙁 Actual behavior
Complains that the result of uhoh could be undefined.
🙂 Expected behavior
switch(true) { case true: } should behave like switch(true) { default: }, probably?
Additional information about the issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the linked TypeScript Playground example as the starting repro. Trace how switch(true) handles the final case true versus default, then verify that the function no longer permits undefined while preserving the A/B/C results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100