impl-wrapper

What problem does it solve?

Defines a disciplined Impl-Client pattern where the Impl acts as a pure delegating wrapper around the underlying Client, ensuring no business logic or HTTP calls exist in the Impl layer.

Core Features & Use Cases

• Enforces a two-class pattern with separate Impl.ts and Client.ts implementations to promote clean separation of concerns.
• Implements lazy, wrapped Producer APIs to cache and decorate producers without moving logic into the Impl.
• Standardizes framework methods like metadata() and isSupported() as placeholders for platform-driven behavior, ensuring consistent contracts.
• Centralizes error handling and HTTP communication in the Client, with the Impl serving as a pass-through.
• Real-world use: apply across multiple services in a monorepo to maintain uniform architecture and reduce boilerplate.

Quick Start

Create the Impl and connect a Client so all business logic remains in the Client and the Impl remains a delegating façade.