Using the container

Service IDs

Service IDs are existing class or interface names. Arbitrary string IDs such as logger are not supported.

get() — resolve a shared service

get() creates a service once and returns the same object on later calls.

Use it for application services that should be shared for the lifetime of this container.

$first = $container->get( ReportService::class );
$second = $container->get( ReportService::class );

var_dump( $first === $second ); // true

make() — create a fresh service

make() resolves the class or its registered definition but never stores the root object.

$preview  = $container->make( ReportService::class );
$preview2 = $container->make( ReportService::class );

var_dump( $preview === $preview2 ); // false

Pass named runtime values when a constructor needs a scalar value:

$mailer = $container->make( Mailer::class, [
	'from' => 'admin@example.test',
] );

Runtime parameters override configured parameters for that call.

has() — check resolvability

has() returns true for a registered service, a previously created service, or an existing concrete class whose entire constructor graph can be resolved.

if ( $container->has( ReportService::class ) ) {
	$report = $container->get( ReportService::class );
}

It returns false for unknown names and classes that need an unresolved dependency or required scalar value.

set() — register a definition

Register interface bindings, existing objects, class aliases, closure factories, or named constructor parameters before first resolving the affected service.

$container->set( LoggerInterface::class, FileLogger::class );

Configure before resolving

Replacing a definition removes the stored object for that ID. It does not rebuild services that were already created and received the old object.

See configuring services for each registration form.

---

Full documentation

For every supported behavior, edge case, exception, and complete example, continue to the container guide.