Avoid Including null or undefined in Type Aliases

Overview

Type aliases should represent something, not "something or nothing."

When you read User, you expect a user - not maybe-a-user. Include null explicitly at usage sites instead of hiding it in type aliases.

When to Use This Skill

• Defining type aliases
• Naming types that include null
• Understanding confusing nullability
• Designing function parameters

The Iron Rule