Shift the boring, repetitive review work to an automated tool, and during your human reviews focus on the business logic, or semantics that no automated tool can analyze.
You might have heard of Option, or Maybe types in other languages. They are used in cases were you might or might not return a value. In PHP, most commonly an object or null is returned in such cases.
I’ve previously talked about using Options on repositories, today I want to talk about another use case of Options and that is simplifying complex algorithms.
It has been a bit more than a month since the initial release of the Review system, and there has been quite a number of improvements, bug fixes, and new cool features since then.
Let’s take a look at the most notable ones.
With the arrival of Travis, you can add continuous integration to all of your PHP projects in the blink of eye. It not only has helped increase code quality, but also made the life of library maintainers a lot easier by providing build information directly in pull requests and thereby decreasing the feedback loop tremendously.
However, Travis suffers from one inherent weakness which it cannot overcome.
The Symfony2 Dependency Injection container has already offered ways to inject dependencies into Doctrine repositories, but they always required boilerplate code, and you could not follow the Doctrine way of retrieving repositories. This is not the case anymore.