[…] reversed. But if you’ve peeked at the source code already, then you know that’s not how this was built. Instead, I opted to use the following tools: GrumPHP for code quality tools. Composer for working with the various packages that are used with GrumPHP. And then the plugin, at a high-level, is structured like […]
Search: “GrumPHP” (Page 2 of 5)
We found 25 results for your search.
It’s one thing to be using PHP CodeSniffer manually but if you’re using a utility such as GrumPHP to check your work before committing it to the repository, then you’re likely going to want to use the version that you’re installing with your project. This assumes that: You are installing PHP CodeSniffer local to […]
I’ve talked about the advantages of using GrumPHP in previous posts. One of the tools that we’ve used in projects for the last year or more is Clover. Photo by Quentin REY on Unsplash Some time between when we started using it and this week, it would always fail to execute every time on my […]
[…] like because: There is a composer.lock file showing that Composer has been executed, It has a vendor directory which shows libraries have been installed via Composer, There is a grumphp.yml file that defines how GrumPHP should work (and I’ll cover this later) when sniffing code. But the gist of the above is the same: You have composer.json and it […]
[…] of a build process for a WordPress project? Given that much of a WordPress project usually includes PHP and JavaScript, you may use a few of these: GrumPHP PHP CodeSniffer PHPMD ESLint And much more. If you’ve configured GrumPHP correctly, it will watch every commit that goes into your repository (even when it’s a local […]
If you are looking for WordPress guides and unbiased reviews, I recommend checking out WPKube. They also have an exclusive deals section.