Extending Symfony2: Controller Utilities
Controllers as a service are a heated topic in the Symfony world. Developers mainly choose to extend the base class, because its much simpler to use and less to write. But less to write is not necessarily true. The Symfony controller base class uses quite a lot of services, if you need them in your controller as a service, you have to inject them: <?php class UserController { public function _cons
Symfony All The Things (Web)
My Symfony Hello World post introduced the smallest possible example of a Symfony application. Using this in trainings helps the participants understand of just how few parts a Symfony application contains. Sure, there are lots of classes participating under the hood, but I don't care about the internals only about the public API. We use microservice architectures for the bepado and PHP Profiler p
Traits are Static Access
In a Twitter discussion yesterday I formulated my negative opinion about traits and Matthew asked me to clarify it: I used to look forward to traits as a feature in PHP 5.4, but after discussions with Kore I came to the conclusion that traits are nothing else than static access in disguise. They actually lead to the exact same code smells. Familiar with the outcome of too much static use, we shoul
On Taming Repository Classes in Doctrine
Over at the easybib/dev Blog Anne posted an entry about their usage of Doctrine Repositories with a growing amount of query responsibilities. I want to respond to this blog post with two alternative approaches, because I have seen the easybib approach multiple times in different projects by different teams and think it can be approved upon a lot. The problems with the approach outlined are: The Re
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
A case for weak type hints only in PHP7
Extending Symfony2: ParamConverter
Doctrine and SOLID
