Propery way to use Slim's dependency container

Question

According to http://www.slimframework.com/docs/tutorial/first-app.html, the slim object is first created, and then the container is gotten and services are added to it.

$app = new \Slim\App(["settings" => $config]);
$container = $app->getContainer();
$container['logger'] = function($c) {
    ...
    return $logger;
};

However, http://www.slimframework.com/docs/concepts/di.html which is specifically about the dependency container is much stronger and states:

You don’t have to provide a dependency container. If you do, however, you must inject the container instance into the Slim application’s constructor.

$container = new \Slim\Container; $app = new \Slim\App($container);

Is one way more proper than the other?

How are services added when using the second approach?

score 2 · Accepted Answer · answered Sep 25 '16 at 10:29

2

Is one way more proper than the other?

There are nealy the same, so in my opinion there is no proper way, but I've doing the second approach, because this way you can add logger and other stuff before you create the actual slim app instance.

How are services added when using the second approach?

The same as using you'r first approach

$container = new \Slim\Container;
$container['logger'] = function($c) {
    ...
    return $logger;
};

$app = new \Slim\App($container);

answered Sep 25 '16 at 10:29

jmattheis

10,494
11
46
58

I think I agree on the second. I also found you can pass a constructor to Container which seems to have to be in format `['slim_setting'=>123,'settings'=>['user_setting'=>321]]` – user1032531 Sep 25 '16 at 11:07

Propery way to use Slim's dependency container

1 Answers1