microsoft / microsoft/TypeScript

TypeScript incorrectly infers logical operation result type with empty string

Open
#45,951 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Domain: check: Control Flow
Dominant language
Go
Stars
111k
Forks
14.4k
Avg merge
1d 19h
Merged PRs (30d)
117

Description

🔎 Search Terms

string logical disjunction type inference string logical inference type infer empty string logical operation type

⏯ Playground Link

Playground link with relevant code

💻 Code
const str: string | undefined = ''

const test = (str || undefined) && {some: 'thing'}
🙁 Actual behavior

Inferred type of operation is

"" | {
    some: string;
} | undefined
🙂 Expected behavior

Inferred type of operation is

{
    some: string;
} | undefined

because (str || undefined) prevents empty string to be returned

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked TypeScript Playground and the code sample using (str || undefined) && {some: 'thing'}. Trace the logical-operation type inference that produces the unexpected "" union member; done means the inferred type is only { some: string } | undefined, with coverage for this example.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.