Learning Laravel - Observations, part 1: The service container

Written by murze.be - - Aggregated on Tuesday June 11, 2019

Matthias Noback wrote down some thoughts on the Laravel container

Laravel's service container looks great. I like the idea that it can figure things out mostly by itself. I like that it's PHP-based, and that its syntax is quite compact. I think that most of the convenience functions (e.g. resolve()) and exotic options (like $this->app->resolving()) should be ignored. The best thing you can do for your application in the long term is to let all your services use dependency injection, and to inject only constructor arguments. This keeps things simple, but also portable to other frameworks with other dependency injection containers, or other architectural styles, when the time is there.


« Xdebug Update: May 2019 - Derick Rethans

murze.be - Using console.table to debug JavaScript … »