effect-option

What problem does it solve?

Many TypeScript codebases using Effect struggle to decide whether optional data should be modeled with Option<T> or as nullable values (T | null | undefined), leading to scattered conventions and subtle bugs.

Core Features & Use Cases

• Establishes clear guidance for when to wrap values in Option versus using nullable types.
• Demonstrates safe interop boundaries with external APIs, DOM, and JSON serialization.
• Use case: modeling a user profile where some fields may be absent but the application must still reason about presence vs absence reliably.

Quick Start

Provide a concise example converting an external payload into Effect<Option<YourType>, Error> and handling missing data with a sensible default.