 |
VOOZH | about |
|
VOOZH | about |
This document covers sophisticated container capabilities that extend beyond basic service binding and resolution. These features include automatic method invocation with dependency injection, lifecycle hooks for customizing resolution behavior, service decoration through extenders, type aliasing, and custom method bindings.
For basic container operations like bind(), make(), and get(), see Container System. For information about how the container loads configuration at bootstrap, see Configuration & Initialization.
The Container class provides several advanced features that enable complex dependency injection patterns, runtime service modification, and flexible callable invocation. These capabilities are built on top of the core Hyperf container while maintaining PSR-11 compliance.
Sources: src/Container.php17-737 src/BoundMethod.php15-222
The advanced features fall into three primary categories:
| Feature Category | Primary Classes/Methods | Purpose |
|---|---|---|
| Method Invocation | BoundMethod, Container::call() | Automatically resolve and inject dependencies when invoking callables |
| Lifecycle Callbacks | beforeResolving(), resolving(), afterResolving() | Hook into the resolution pipeline to modify behavior |
| Extensibility | extend(), alias(), bindMethod() | Decorate instances, create name aliases, override method resolution |
Sources: src/Container.php17-737 src/BoundMethod.php15-222
The BoundMethod class provides automatic dependency injection for arbitrary callables. When you call Container::call(), it delegates to BoundMethod::call() which resolves all callable parameters automatically.
Sources: src/BoundMethod.php25-74 src/Container.php437-440 src/Container.php264-295
When BoundMethod resolves parameters for a callable, it follows a specific priority order:
| Priority | Source | Description |
|---|---|---|
| 1 | Explicit parameters (by name) | Parameters passed to call() matching parameter name |
| 2 | Explicit parameters (by position) | Parameters passed to call() matching parameter position |
| 3 | Explicit parameters (by type) | Parameters passed to call() matching the type hint |
| 4 | Default values | Parameter has a default value defined |
| 5 | Container resolution | Container can resolve the type hint |
| 6 | Nullable | Parameter allows null value |
| 7 | Exception | Throws BindingResolutionException |
The resolution logic is implemented in getDependencyParameters() at src/BoundMethod.php76-115
For detailed information about method invocation, see Method Invocation & Dependency Injection.
Sources: src/BoundMethod.php76-115
The container provides three callback hooks that fire during service resolution: before resolving, during resolving, and after resolving. Each hook supports both global callbacks (fired for all resolutions) and type-specific callbacks (fired only for specific types).
Sources: src/Container.php109-132 src/Container.php467-514 src/Container.php522-610
The container maintains six separate arrays for lifecycle callbacks:
Sources: src/Container.php59-94
For detailed information about registering and using lifecycle callbacks, see Lifecycle Callbacks.
Beyond lifecycle callbacks, the container provides three additional extensibility mechanisms:
Extenders allow you to modify or decorate resolved instances. Unlike lifecycle callbacks which observe resolution, extenders transform the instance.
extenders array at src/Container.php45extend() method at src/Container.php314-324make() at src/Container.php125-127Aliases create alternative names for service bindings, enabling flexible type references.
aliases array (alias → abstract) at src/Container.php31abstractAliases array (abstract → aliases[]) at src/Container.php38alias() method at src/Container.php374-383getAlias() method at src/Container.php623-628Method bindings allow you to override how specific methods are invoked when called through Container::call().
Sources: src/Container.php264-295 src/BoundMethod.php152-168
For comprehensive coverage of these features, see Extenders, Aliases & Method Bindings.
The following table shows how advanced features interact with each other:
| Feature | Respects Aliases | Fires Callbacks | Uses Extenders | Can Override |
|---|---|---|---|---|
make() | ✓ | ✓ | ✓ | Via callbacks/extenders |
call() | ✗ | ✗ | ✗ | Via method bindings |
extend() | ✓ | ✗ | ✗ | Modifies existing extenders |
alias() | ✗ | ✗ | ✗ | N/A |
bindMethod() | ✗ | ✗ | ✗ | Completely overrides method |
Sources: src/Container.php109-132 src/Container.php437-440 src/Container.php314-324 src/Container.php374-383 src/Container.php272-275
When a service binding is updated, the container provides mechanisms to notify dependent code and refresh instances:
Rebound callbacks fire whenever a binding is replaced:
rebinding() method at src/Container.php388-397reboundCallbacks array at src/Container.php52rebound() method at src/Container.php412-419bind(), instance(), extend() when binding already existsThe refresh() method provides a convenient way to update a property or call a setter when a service is rebound:
This is implemented at src/Container.php402-407 and internally uses rebinding().
Sources: src/Container.php388-419 src/Container.php243-259 src/Container.php329-349 src/Container.php314-324
Method bindings enable conditional or contextual method execution:
Implementation at src/Container.php272-287
Extenders enable the decorator pattern without modifying service definitions:
Implementation at src/Container.php314-324
Lifecycle callbacks allow type-specific initialization logic:
Implementation at src/Container.php485-496 src/Container.php552-562
Sources: src/Container.php272-287 src/Container.php314-324 src/Container.php485-496 src/Container.php552-562
The advanced container features provide powerful mechanisms for:
These features are explored in detail in the following subsections:
BoundMethod and callable resolutionRefresh this wiki