Beginning the build of a GatsbyJS theme
I finally have my workspace set up, allowing me to begin serving content from one Drupal Commerce API server to three GatsbyJS apps.
I finally have my workspace set up, allowing me to begin serving content from one Drupal Commerce API server to three GatsbyJS apps.
As I have begun working with GatsbyJS once again, I am trying to find a way to work with GatsbyJS and Drupal locally in a somewhat streamlined fashion. Honestly, serving Drupal over PHP's built-in server and using the gatsby develop and gatsby serve command work just fine. But, I love tooling.
I have been tracking down an interesting quirk when parsing JSON:API resources with the Drupal source plugin for GatsbyJS. I have a test environment with the JSON:API Schema module installed and was receiving errors about data in the links property.
The Drupal community has taken to GatsbyJS, the React framework that lets you easily build static (and more) websites (or applications.) And, honestly, this makes a lot of sense. Drupal is a great content management system and it even has ways to create microsites within one installation (thanks to techniques like the Domain module.)
The end of May brought two exciting releases for PHPStan and the PHPStan Deprecation Rules extension. With the version of PHPStan v0.11.8, descriptions added to the @deprecated tag can be parsed and returned in rule checks.
Last month I wrote about writing better Drupal code with static analysis using PHPStan.