unyo-dependency-injection

To organize dependency injection with GetIt, centralize all registrations for services, repositories, cubits, and notifiers within a dedicated locator. This standardizes resolution and debugging while applying two-phase initialization to safely handle both synchronous and asynchronous dependencies.

Two-phase initialization in GetIt splits locator setup into setupLocator before runApp and setupLocatorAfterHiveInit after Hive initializes. This accommodates async platform dependencies and Hive storage, ensuring platform and storage-dependent components are registered safely.

Use GetIt singletons for eager global instances, lazy singletons for resource-heavy objects created on first access, and factories for fresh instances on every resolution. Applying these registration types with named instances and lifecycle rules ensures safe and predictable wiring.

Wiring a new cubit and notifier into a GetIt locator requires registering both components in the correct initialization phase. You must specify the appropriate registration type, apply naming conventions, and resolve any repository dependencies safely to prevent missing registrations.

GetIt supports async singletons for Flutter applications requiring asynchronous dependency registration. This is utilized during the second initialization phase after Hive initializes, allowing the locator to safely resolve components that depend on async platform services or local storage.

GetIt dependency injection fails with missing registrations or circular dependencies when components are improperly scoped or resolved before initialization. Guardrails against these common pitfalls require strict adherence to two-phase initialization, correct registration types, and established naming conventions.