uw-dependency-injection

Decoupling Unity components via dependency injection uses a container like Reflex to wire services through inversion-of-control instead of direct instantiation, creating testable code.

A DI-first architecture in Unity uses per-feature installers and container bindings to manage dependencies, enabling cross-feature communication via Commands to avoid direct cross-references.

To set up Reflex, install the framework, create a feature Installer to bind interfaces to implementations, and wire dependencies across features using constructor injection and scoped lifetimes.

Use a DI-first architecture for medium to large Unity projects needing cross-feature coordination, scalable bindings, and testable code, requiring a ProjectConfig.yaml with architecture_pattern set to di-first.

Handle cross-feature communication in Unity without direct references by using Commands within a DI-first architecture, allowing features to interact through bound interfaces rather than tight coupling.

Yes, this DI-first approach requires a ProjectConfig.yaml with architecture_pattern set to di-first, Reflex as the DI framework, and adherence to specific naming conventions and coding standards.