NonNullable type in Typescript

Introduction

The NonNullable type helps you remove null and undefined from a type. This makes sure your values are always real and not empty.

When you want to make sure a variable never holds <code>null</code> or <code>undefined</code>.

When you get data that might be empty but you want to work only with real values.

When you want to avoid errors caused by missing values in your program.

Syntax

Typescript

NonNullable<Type>

Type is the original type you want to clean up.

The result is a new type without null and undefined.

Examples

This removes null and undefined from the type, so CleanString is just string.

Typescript

type CleanString = NonNullable<string | null | undefined>;

OnlyNumber will be just number, no null.

Typescript

type NumberOrNull = number | null;
type OnlyNumber = NonNullable<NumberOrNull>;

DefiniteBoolean is just boolean, no undefined.

Typescript

type MaybeBoolean = boolean | undefined;
type DefiniteBoolean = NonNullable<MaybeBoolean>;

Sample Program

This program defines a function that only accepts strings without null or undefined. It prints the length of the string. Trying to pass null or undefined causes an error.

Typescript

type Input = string | null | undefined;

function printLength(value: NonNullable<Input>) {
  console.log(`Length is ${value.length}`);
}

printLength("hello");
// printLength(null); // Error: Argument of type 'null' is not assignable to parameter of type 'string'.
// printLength(undefined); // Error: Argument of type 'undefined' is not assignable to parameter of type 'string'.

Important Notes

NonNullable only removes null and undefined, other types stay the same.

This helps catch mistakes early by making sure values are always present.

Summary

NonNullable removes null and undefined from types.

Use it to make sure your variables always have real values.

It helps prevent errors caused by missing or empty values.

Practice

1.

What does the NonNullable type do in TypeScript?

easy

A. Converts a type to a string

B. Adds null and undefined to a type

C. Removes null and undefined from a type

D. Makes a type optional

Solution

1. Step 1: Understand the purpose of NonNullable

   The NonNullable type removes null and undefined from a given type, ensuring the value is always defined.

2. Step 2: Compare options with definition

   Only Removes null and undefined from a type correctly describes this behavior; others describe different or incorrect behaviors.

3. Final Answer:

   Removes null and undefined from a type -> Option C

4. Quick Check:

   NonNullable removes null and undefined [OK]

Hint: Remember: NonNullable cuts out null and undefined [OK]

Common Mistakes:

• Thinking it adds null or undefined
• Confusing it with making types optional
• Assuming it converts types to strings

2.

Which of the following is the correct syntax to use NonNullable on a type T?

easy

A. NonNullable(T)

B. NonNullable{T}

C. NonNullable[T]

D. NonNullable<T>

Solution

1. Step 1: Recall TypeScript generic syntax

   TypeScript uses angle brackets <> to apply generic types, like NonNullable<T>.

2. Step 2: Match options with correct syntax

   NonNullable<T> uses the correct generic syntax. Options A, C, and D use incorrect brackets or parentheses.

3. Final Answer:

   NonNullable<T> -> Option D

4. Quick Check:

   Generic types use <> brackets [OK]

Hint: Use angle brackets for generics: NonNullable<T> [OK]

Common Mistakes:

• Using parentheses instead of angle brackets
• Using square brackets or curly braces
• Confusing function call syntax with type syntax

3.

What is the type of value after this code runs?

type MaybeString = string | null | undefined;
const value: NonNullable<MaybeString> = "hello";

medium

A. string

B. null | undefined

C. string | null | undefined

D. never

Solution

1. Step 1: Understand the original type

   MaybeString can be string, null, or undefined.

2. Step 2: Apply NonNullable to remove null and undefined

   Using NonNullable<MaybeString> removes null and undefined, leaving only string.

3. Final Answer:

   string -> Option A

4. Quick Check:

   NonNullable removes null and undefined, leaving string [OK]

Hint: NonNullable removes null and undefined from union types [OK]

Common Mistakes:

• Thinking the type still includes null or undefined
• Confusing NonNullable with Partial or Required
• Assuming the type becomes never

4.

Identify the error in this code snippet:

type User = { name: string | null };
type CleanUser = NonNullable<User>;

medium

A. There is no error; code is correct

B. The syntax for NonNullable is incorrect

C. NonNullable removes null from properties inside objects automatically

D. NonNullable cannot be applied to object types directly

Solution

1. Step 1: Understand what NonNullable does

   NonNullable removes null and undefined from a type itself, not from nested properties.

2. Step 2: Analyze the code

   The code is syntactically correct. NonNullable<User> results in the same type as User since User is not a union including null or undefined at the top level.

3. Final Answer:

   There is no error; code is correct -> Option A

4. Quick Check:

   Code compiles without errors [OK]

Hint: NonNullable can be applied to object types but does not clean nested properties [OK]

Common Mistakes:

• Believing NonNullable cleans nested properties automatically
• Thinking the syntax for NonNullable is incorrect
• Thinking NonNullable cannot be applied to object types

5.

Given this type, how can you create a new type NonNullUser where the email property cannot be null or undefined using NonNullable?

type User = {
  id: number;
  email: string | null | undefined;
};

hard

A. type NonNullUser = NonNullable<User>

B. type NonNullUser = { id: number; email: NonNullable<string | null | undefined> }

C. type NonNullUser = { id: number; email: string }

D. type NonNullUser = { id: number; email: string | null }

Solution

1. Step 1: Understand the goal

   We want to keep id as is, but make email exclude null and undefined.

2. Step 2: Apply NonNullable to the email property only

   Using NonNullable<string | null | undefined> on email removes null and undefined, leaving just string.

3. Step 3: Check other options

   type NonNullUser = NonNullable<User> removes null/undefined from the whole User type, which does not affect nested properties. type NonNullUser = { id: number; email: string } changes the type but does not use NonNullable. type NonNullUser = { id: number; email: string | null } still allows null.

4. Final Answer:

   type NonNullUser = { id: number; email: NonNullable<string | null | undefined> } -> Option B

5. Quick Check:

   Apply NonNullable only to the property needing it [OK]

Hint: Use NonNullable on specific properties, not whole object [OK]

Common Mistakes:

• Applying NonNullable to the whole object type
• Not removing null and undefined from email
• Changing type without NonNullable