Why Non-distributive conditional types in Typescript? - Purpose & Use Cases

The Big Idea

What if you could tell TypeScript to treat a group of types as one, avoiding confusing splits and mistakes?

The Scenario

Imagine you have a list of different fruits and you want to check if each fruit is an apple or not. Doing this by hand means checking each fruit one by one and writing separate code for each case.

The Problem

Manually checking each item is slow and easy to mess up. If the list grows or changes, you have to rewrite or copy-paste code many times, which leads to mistakes and wasted time.

The Solution

Non-distributive conditional types let you write one smart rule that applies to the whole list at once, without splitting it up. This saves time and keeps your code clean and easy to change.

Before vs After

✗ Before

type Check<T> = T extends 'apple' ? 'Yes' : 'No';
type Result = Check<'apple' | 'banana'>; // 'Yes' | 'No' (distributes)

✓ After

type Check<T> = [T] extends ['apple'] ? 'Yes' : 'No';
type Result = Check<'apple' | 'banana'>; // 'No' (no distribution)

What It Enables

This concept lets you control how TypeScript checks types, making your code smarter and more precise when working with groups of types.

Real Life Example

When building a form that accepts different input types, you can use non-distributive conditional types to apply validation rules to the entire input type at once, instead of handling each input type separately.

Key Takeaways

Manual checks for each type are slow and error-prone.

Non-distributive conditional types apply conditions to whole types without splitting.

This leads to cleaner, safer, and easier-to-maintain code.

Practice

1. What does a non-distributive conditional type in TypeScript do differently compared to a distributive conditional type?

easy

A. It converts all types to string before evaluation.

B. It always distributes the condition over each member of the union type.

C. It only works with primitive types, not unions.

D. It evaluates the condition on the entire union type as a whole, not on each member separately.

Solution

1. Step 1: Understand distributive conditional types

   Distributive conditional types apply the condition to each member of a union type separately.

2. Step 2: Understand non-distributive conditional types

   Non-distributive conditional types evaluate the condition on the entire union type as a single entity, not distributing over members.

3. Final Answer:

   It evaluates the condition on the entire union type as a whole, not on each member separately. -> Option D

4. Quick Check:

   Non-distributive = whole union check [OK]

Hint: Non-distributive means no splitting union, check whole type [OK]

Common Mistakes:

• Thinking conditional always distributes over unions
• Confusing non-distributive with type narrowing
• Assuming it only works on primitives

2. Which syntax correctly defines a non-distributive conditional type in TypeScript?

easy

A. type NonDist<T> = T | string ? true : false;

B. type NonDist<T> = T extends string ? true : false;

C. type NonDist<T> = [T] extends [string] ? true : false;

D. type NonDist<T> = T & string ? true : false;

Solution

1. Step 1: Recognize non-distributive syntax

   Wrapping the type parameter in a tuple, like [T], prevents distribution over unions.

2. Step 2: Compare options

   type NonDist<T> = [T] extends [string] ? true : false; uses [T] extends [string], which is the correct non-distributive syntax. type NonDist<T> = T extends string ? true : false; distributes over unions. Options C and D are invalid conditional syntax.

3. Final Answer:

   type NonDist<T> = [T] extends [string] ? true : false; -> Option C

4. Quick Check:

   Tuple wrapping disables distribution [OK]

Hint: Wrap type in tuple [T] to prevent distribution [OK]

Common Mistakes:

• Not wrapping type in tuple, causing distribution
• Using invalid conditional syntax
• Confusing union with intersection in condition

3. Given the code:

type Test<T> = T extends string ? 'yes' : 'no';
type Result = Test<'a' | number>;

What is the type of Result?

medium

A. 'yes' | 'no'

B. 'yes'

C. 'no'

D. Error

Solution

1. Step 1: Understand distributive conditional types

   Since T is a union 'a' | number, the condition distributes over each member.

2. Step 2: Evaluate each member

   'a' extends string is true, so 'yes'; number extends string is false, so 'no'. Combined result is 'yes' | 'no'.

3. Final Answer:

   'yes' | 'no' -> Option A

4. Quick Check:

   Distributes over union = 'yes' | 'no' [OK]

Hint: Conditional distributes over union unless wrapped [OK]

Common Mistakes:

• Assuming whole union checked at once
• Expecting only 'yes' or only 'no'
• Confusing union with intersection

4. Identify the error in this non-distributive conditional type:

type NonDist<T> = T extends [string] ? true : false;

medium

A. It incorrectly checks if T extends a tuple containing string, not preventing distribution.

B. It correctly prevents distribution by wrapping T in a tuple.

C. It causes a syntax error because of missing brackets.

D. It always returns false regardless of T.

Solution

1. Step 1: Analyze the condition

   The condition checks if T extends [string], a tuple type, not wrapping T.

2. Step 2: Understand distribution prevention

   To prevent distribution, T itself must be wrapped in a tuple: [T] extends [string]. This code does not do that, so distribution is not prevented.

3. Final Answer:

   It incorrectly checks if T extends a tuple containing string, not preventing distribution. -> Option A

4. Quick Check:

   Wrap T, not string, to prevent distribution [OK]

Hint: Wrap T in tuple, not the type to check [OK]

Common Mistakes:

• Wrapping the wrong side of extends
• Confusing tuple with type wrapper
• Assuming syntax error instead of logic error

5. How can you write a non-distributive conditional type that checks if a union type T is exactly string | number (no more, no less)?

hard

A. type Exact<T> = T extends string | number ? true : false;

B. type Exact<T> = [T] extends [string | number] ? ([string | number] extends [T] ? true : false) : false;

C. type Exact<T> = T extends [string | number] ? true : false;

D. type Exact<T> = [T] extends [string] | [number] ? true : false;

Solution

1. Step 1: Prevent distribution with tuple wrapping

   Wrapping T in a tuple [T] prevents distribution over unions.

2. Step 2: Use mutual assignability checks

   Check [T] extends [string | number] and [string | number] extends [T] to ensure exact match, no extra or missing types.

3. Final Answer:

   type Exact<T> = [T] extends [string | number] ? ([string | number] extends [T] ? true : false) : false; -> Option B

4. Quick Check:

   Tuple wrap + mutual extends = exact type check [OK]

Hint: Wrap T and check both extends directions for exact match [OK]

Common Mistakes:

• Not preventing distribution, causing partial matches
• Checking only one extends direction
• Using incorrect tuple wrapping