In the latest months I wrote multiple times, in different projects, code migrating PHPUnit toward major version 6. This upgrade is harder than the previous one, since in this version it was introduced a big breaking change: all classes got (finally!) namespaced. This means that any usage of those classes in your project needs to be updated. It may seem a simple find & replace job, but since you need to introduce at least one use PHPUnit\Framework\TestCase line at the top of each one of your test classes, it’s a boring and a little more than trivial task; also, upgrading it in a single big jump may not be feasible or prudent, especially in the case of open source or distributed libraries, where backward compatibility and support for old PHP versions must be ensured.
Articles in category: English
A few days ago I stumbled on a strange tweet that was highlighting a controversy about scalar type hints. Scalar type hints & return types vs no scalar type hints & return types is #PHP's new spaces vs tabs — Cees-Jan 🔊 Kiewiet (@WyriHaximus) 19 maggio 2017 After asking references about this, someone alluded to this very short video: “PHP Bits: Visual Debt” (it’s only 3 minutes, please watch it before continue reading).
Like clockwork, on May we head up to Verona to attend the phpDay conference; this time it was on May 12th and 13th. We met a lot of new people and known fellow PHP developers, and like previous years, we wanted to write down a light summary; like the previous ones, this won’t be a full “review” of the conference, but an highlight of the talks that captured most of our attention, or what we found more valuable for our everyday work.
Ten days ago #FacileHack 2017 came to its conclusion; this was the second edition of the hackathon organized by Facile.it. Holding an event of this kind has allowed us to see, work and discuss with many very diverse teams, made up of programmers, designers and marketers. The hackathon’s theme for this year was connectivity: our site offers the comparation between internet access services, and we have decided to put this at the center of the competition.
Here at Facile.it we are constantly dealing with a lot of forms: we use them to collect various information and data needed to feed our in-house comparing algorithms. These forms could be really complex, having multiple rules and dependencies between fields, and they are likely to be changed and tuned frequently. When I joined Facile.it, a lot of forms within the Android app needed to be updated or modified and sticking with the existing strategy would have required me to do a lot of work just to add or remove a simple field.