Overview for 'matthiasnoback'
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
About interface segregation, dependency inversion and package stability You are creating a nice reusable package. Inside the package you want to use events to allow others to hook into your own code. You look at several event managers that are available. Since you are somewhat familiar with the Sym…
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
Recently I realized that some of the problems I encountered in the past could have been easily solved by what I'm about to explain in this post. The problem: an event listener introduces a circular reference The problem is: having a complicated graph of service definitions and their dependencies,…
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
Almost a year ago, on September 4th, in front of a live audience, I published my first book "A Year With Symfony". Since the first release, well over a 1000 people have read it. In February of this year, I added a new chapter to the book (about annotations). A third edition? Flipping through the pa…
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
Fernando Arconada interviewed me about the subject of testing. He is writing a book about testing Symfony2 applications: Testing para Aplicaciones Symfony2. Fernando will translate this interview to Spanish and and add it to his book, together with the articles in my A better PHP testing experience…
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
In the introduction to this series I mentioned that testing object interactions can be really hard. Most unit testing tutorials cover this subject by introducing the PHPUnit mocking sub-framework. The word "mock" in the context of PHPUnit is given the meaning of the general concept of a "test doubl…
Written by Matthias Noback
/ Original link
on Oct. 12, 2014
This is a response to Peter Petermann's article Composer and virtual packages. First, let's make this totally clear: I don't want to start an Internet war about this, I'm just pointing out some design issues that may arise from using Composer's provide option in your package's composer.json file.…