BloomContainer class

Lightweight, high-performance Dependency Injection container for Bloom.

Architecture & Scoping Model

BloomContainer supports three binding lifecycles:

1. Transient (provide): The factory is executed every time inject is called, producing a fresh instance each time.
2. Singleton (provideSingleton): The factory is executed once, and the resulting instance is cached and reused across all subsequent inject calls. Can be created lazily on first resolution (default) or eagerly upon registration (lazy: false).
3. Value (provideValue): An already-instantiated object is registered directly.

Hierarchical Resolution

Containers can be nested with an optional parent. When resolving a type T:

1. The container checks for local test overrides (override / overrideType).
2. The container checks its own local bindings.
3. If not found locally and parent exists, resolution delegates up to the parent.
4. If nowhere found, inject throws a descriptive StateError (or injectOrNull returns null).

Testing & Overrides

Test harnesses can register overrides via override or BloomTestScope that take precedence over existing bindings without altering production container setup.

Example

final container = BloomContainer();

// Register services
container.provideSingleton<DatabaseService>(() => PostgresService());
container.provide<UserRepository>(() => UserRepository(container.inject<DatabaseService>()));
container.provideValue<String>('https://api.example.com');

// Resolve dependencies
final userRepo = container.inject<UserRepository>();