Back at #mageuc19 I gave a talk about various PHP tools that help you to manage the quality of your (Magento) project. One of the tools I mentioned is CaptainHook, a tool written in PHP to manage your git hooks. Whilst this is not a QA tool per se, it still made sense to showcase it as most QA tools do run via CaptainHook in our projects. That means tools like PHPUnit, Codesniffer, Security Checker or tools like PHPStan or Psalm.
On the 6th of December, I was given the opportunity to attend my first React Day in Berlin. It is one of the largest React focussed conferences in the world, with ~500 attendees this year.
Since it started all the way back in 2015 the MageUnconference has been high on my priority when it comes to Magento events. This year I was super excited not just to be back but also to bring along one of my new colleagues for his first MageUnconf experience.
On the 30th of November and the 1st of December FireGento invited the Magento Community to Cologne for the 5th edition of the Mage Unconference.
Documenting CSS code is often not that easy. Especially structuring big CSS files can be a challenge. Living styleguides can be a solution and there are many different generators for creating them. Also pattern libraries can be a solution, for example based on Patternlab.
For quite a while I wanted to upgrade the Docker setup for the open-source Force Login module we develop for Magento 2. We were using a very old version of Mark Shust's Docker Configuration for Magento setup. Since there were a lot of changes how things work nowadays, the upgrade was not simple and came with a few side-effects. The latest version of the setup requires Magento to be checkout out locally and to be mounted in the container. If you develop a Magento application that totally makes sense, but for our module, it felt it makes more sense to have the Magento application code in the container as it used to be in the old setup. This led to a bunch of changes that I'll cover below.
A few weeks back at MageTestFest 2019 in Florence, I gave a presentation on QA tools I like and gave some insights how they can be used in a Magento project. One of the tools I mentioned was PHPStan - a static analysis tool. PHPStan helps you to detect a lot of problems in your code due to using wrong types, calling methods that might not exist, passing the wrong number or types of arguments to methods and so on. PHPStan is also able to create your own rule sets of what behavior you want to check for.
These days we get more and more in situations where we have to push our code into Git repositories of our customers, either because the customer wants access to the source code or because we are working closely with their in-house team. Maintaining our own local copy of the source code and constantly keeping our copy in sync is a no brainer with Git.
One of our customers asked us to remove the delete option from the mass action element for the product grid. What sounded like a simple task evolved into a lot of debugging and testing. Apparently removing the mass action option from the xml configuration does not work even though a lot of StackOverflow posts say so. The only way that worked for me, was to do it programmatically like this:
Back at MageTestFest in Florence, I introduced the audience to a tool called Captain Hook for managing Git hooks. In the QA section of my talk, the question was raised why I have not recommended to use GrumPHP. A valid question since all the QA tools I talked about are already supported by GrumPHP out-of-the-box.