magento-di

Magento 2 Dependency Injection

Before writing code

Fetch live docs:

1. Web-search site:developer.adobe.com commerce php development components dependency-injection for the DI guide
2. Fetch https://developer.adobe.com/commerce/php/development/ and navigate to DI documentation
3. Web-search site:developer.adobe.com commerce php development build di-xml for di.xml reference

Conceptual Architecture

How DI Works in Magento

Magento's Object Manager reads di.xml configurations and automatically injects dependencies into class constructors. You declare what you need; the framework provides it.

Constructor injection is the primary pattern — declare dependencies as constructor parameters with type hints.

di.xml Scope

di.xml files are area-scoped:

• etc/di.xml — global (all areas)
• etc/frontend/di.xml — storefront only
• etc/adminhtml/di.xml — admin panel only
• etc/webapi_rest/di.xml — REST API only
• etc/webapi_soap/di.xml — SOAP API only

Types

Configure constructor arguments for a specific class:

• Override default values
• Inject different implementations per area
• Argument types: string, boolean, number, const, null, object, array, init_parameter

Virtual Types

Create class variations without writing new PHP files:

• Same base class with different constructor arguments
• Only exists in DI configuration
• Cannot be injected by classname directly (use as a type attribute value)
• Reduces code duplication significantly

Preferences

Map an interface to a concrete implementation:

• <preference for="InterfaceName" type="ConcreteClassName" />
• Global preference applies everywhere unless overridden by area-specific di.xml
• Foundation of Magento's interface-based programming

Argument Types

Type	Description
string	String value
boolean	true or false
number	Integer or float
const	PHP constant value
null	Null value
object	Another class instance (injected)
array	Array of mixed argument types
init_parameter	Value from Magento\Framework\App\DeploymentConfig