no-null-in-aliases

What problem does it solve?

Type aliases should represent actual values and not be used to hide nullability. They can obscure nullability and lead to runtime errors. 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.

Core Features & Use Cases

• Clear nullability at usage sites: prefer User | null at the point of use.
• Avoid ambiguous type aliases: keep top-level types without | null and handle nullability where needed.
• Refactoring safety: easier reading and safer code when nullability is explicit.
• Use case examples: when defining type aliases for API responses or domain models, ensure that nullability is explicit at the usage boundary.

Quick Start

Review your type aliases and replace any pattern like Type = { ... } | null with a plain type and use Type | null where needed.