I realize this is a scope thing, and a fundamental part of PHP I’m sure, but I’m learning as I go here and I’m a little confused. Part of the tutorial has you define some config settings and plug them into the App instance:
How would I also access this from within a class?
class RandomAuthenticator implements AuthenticatorInterface {
public function __invoke(array $arguments) {
// $this->get(‘settings’)[‘custom’][‘minPasswordLength’] won’t work here.
return (bool)rand(0,1);
}
}
This would result an error like this:
Call to undefined method RandomAuthenticator::get() in /var/www/html/config/middleware.php on line 16
To access it from a class, it needs to be given to the class as currently the class doesn’t know about it. If RandomAuthenticator is in your container you can define it there. To see an example of this, checkout the Slim-Skeleton.
In that example, the Slim\Views\PhpRendered class is being given the settings for the template path. Then in your RandomAuthenticator class you would accept it through the constructor. You can find an example of that in this other Skeleton project.
In that example see how the view is being accepted in the constructor, setup as $this->view and then used later.
I’m wondering !! Last couple of day I tried some xdebug things and saw that there a reference to the Slim App object in the $GLOBALS namespace …
I was searching for a good way to have acces to the database from several points :
In my Controllers (so I set et self.db in the constructor and use D.I.)
In my Models (same thing).
Now i’m moving my DB logic to specific classes for each Model ( mimic the repository in Symfony I think ).
So first think with moving things to the Repository was to test :
wich works pretty well (db is a container object wich returns a PDO instance)…
But i’d like to have some review about this practice. Doesn’t it look like Slim::getInstance() in Slim 2.x ?
What problem can I get (like having multiple PDO instances). I’ve tried
$pdo = $GLOBALS[“app”]->getContainer()->get(‘db’);
$pdo2 = $GLOBALS[“app”]->getContainer()->get(‘db’);
var_dump($pdo == $pdo2); die;
It returns True (but as it’s only initialized it might be misleading).
I’m feeling that i’m killing good pratices here. Any opinion ?
Thanks
@robrothedev Yes, that’s how i’m currently doing it. But instead of using D.I. I was wondering about using the $GLOBALS namespace wich contains the ‘app’ reference, wich means an access point to the controller without D.I.
Here’s my bootstrap:
$app = new \Slim\App($app_settings);
$container = $app->getContainer();
An exemple of a controller in wich a $container is injected :
class BaseController
{
protected $container;
protected $modelInstance;
public function __construct($container)
{
$this->container = $container;
}
public function __get($property)
{
if ($this->container->{$property}) {
return $this->container->{$property};
}
}
// controller’s methods // …
}
Now trying to avoid always passing $this->container to my models and controllers, i’ve tested this way :
class CompanyRepository
{
protected static $view = "v_company";
public static function get($page, $itemPerPage)
{
$pdo = $GLOBALS["app"]->getContainer()->get('db');
$sth = $pdo->prepare("SELECT legal_name FROM " . CompanyRepository::$view . ";");
$sth->execute();
$r = $sth->fetchAll();
return $r;
}
}
Here I use the $GLOBALS variables to get the App refernce wich gives me the container from wich I get the DB ‘instance’.
I’ve tried to monitor the DB acces and it seems that I only get 1 connection no matter if in the same execution I call the database from the D.I. container in the Controller and in the static GLOBALS way. So it seems that I get the same PDO object. Wich could be cool !
Your method works but there seems to be a lot of heavy dependency with Slim and your source code. I would advocate dependency injections for classes rather than accessing Slim $GLOBALS.
@Mout I think Rob Allen’s Tweet sums up Slim development pretty well. You want to write your components separately and then integrate them into Slim rather than writing Slim specific code, although Controllers are a bit of an exception.
I would lean on dependency injection like this:
$di = new Slim\Container;
$di['pdo'] = function() {
return new App\DB($host,$user,$pass,$name);
};
$di['companyRepo'] = function($di) {
return new App\CompanyRepository($di->pdo);
};
$di['CompanyCtrl'] = function($di) {
return new CompanyController($di->companyRepo);
};
$app = new Slim\App;
$app->get('/company','CompanyCtrl:get');
// classes
class CompanyRepository {
public function __construct($pdo) {
$this->pdo = $pdo;
}
public function get($view) {
$sth = $this->pdo->prepare("SELECT legal_name FROM " . $view);
$sth->execute();
return $sth->fetchAll();
}
}
class CompanyController {
public function __construct($companyRepo) {
$this->companyRepo = $companyRepo;
}
public function get($request,$response) {
$view = "v_company";
$record = $this->companyRepo->get($view);
// return your page with the record data
}
}
