-
Notifications
You must be signed in to change notification settings - Fork 25
Running with service manager #44
Comments
From your console PHP script, chdir to the root, bootstrap composer autoload, and call the container script. Like below: <?php
use Psr\Container\ContainerInterface;
chdir(__DIR__ . '/../');
require_once 'vendor/autoload.php';
/** @var ContainerInterface $container */
$container = require 'config/container.php'; Later on in the script you can use it in the handler definition: <?php
use Zend\Console\Console;
// ...
$routes = [
[
'name' => 'my-route',
'route' => '[--foo=]',
'description' => 'Some really cool feature',
'short_description' => 'Cool feature',
'options_descriptions' => [
'foo' => 'Lorem Ipsum',
],
'defaults' => [
'foo' => 'bar',
],
'handler' => function($route, $console) use ($container) {
$handler = $container->get(My\Fully\Qualified\Class\Name::class);
return $handler($route, $console);
}
],
// ...
] |
can dispatcher handler the container (servicemanager) stuff ? this look's dirty. loading container in other file, then on route.config.php reuse the container variable. |
Using closures is valid PHP and an acceptable way to provide lazy-loading. It's also possible to extend the zf-console dispatcher to do this sort of thing, and that would be an interesting patch for us to consider. |
adding handlermanager similar to controllermanager would be nice ( not sure if it is possible to add eventmanager ). handlermanager will use it's own config array instead of putting every handler inside service_manager config. |
Could you gave example how to do dependency injection from service manager ( container interop ) that define in the configuration to the handler ?
The text was updated successfully, but these errors were encountered: