📘 Understanding Drupal: A Complete Guide to Caching Layers — my new book is out now!
There is a lot happening in the world. I am not talking about COVID-19, which is still a pandemic and hasn't magically become mild. But, I am talking about the civil unrest in the United States. Some are frightened, some are angry in solidarity, some are angry and do not agree. I am hopeful. I firmly believe we have a problem in the United States with our militarized police forces.
I write a lot of tests for all of my Drupal code. I try to live by Test Driven Development. It delivers cleaner code. It helps define your architecture without full implementation details. I also despise clicking and manually testing things.
Earlier this month, I signed up as a sponsor for Jeff Geerling on GitHub.
Every year I dedicate a block of time to provide new features and improve ContribKanban, beyond regular maintenance to keep dependencies up to date. This year brings some significant changes, which I am excited about!
Heads up! After using this, I have found myself needing to run `gatsby clean` before `develop` or `build` when using this approach.
Well. I had a great idea to use Gatsby's StaticQuery component for catalogs and product displays. I was hoping to also use the useStaticQuery hook for experimenting with shadowing. There is just one problem.
Even though Gatsby is a static site generator, it can be used to build dynamic applications. Gatsby is, after all, just a framework for building a React application. It just happens to be extremely opinionated and generates an artifact that is a static site. To me, "dynamic" means that an application maintains some form of state.
At the beginning of December, Ondřej Mirtes released PHPStan 0.12! 0.12 brought about many changes. However, 🙃, it broke the PHPStan Drupal extension.