Over the last few weeks, I’ve been blogging a bit less. This isn’t so much because I’ve nothing to say, it’s because I’ve been heads down on a number of different projects and trying to learn a couple of new technologies (all of which will contribute back to WordPress).
In the middle of doing this, I realized I’d not shared two useful tools for WordPress development – specifically, a REST API client and a database front-end.
Yes, there are a numerous tools out there are you probably already have your favorites. Here, though, are the two that I’ve been using the most.
In the most recent post of this series (which is admittedly some time ago), I talked at length about Composer and its lock file.
I recommend reading the previous two articles because Composer is eventually going to play a role in this material that this and future posts are going to share. But if you opt not to catch up on them (or are already familiar with Composer) then the gist of the previous posts are, respectively, as follows:
I don’t recommend checking the vendor directory into your repository. That can become a huge directory later, and it can undermine the whole purpose of Composer.
With that said, there are numerous dependencies or packages that we can install that help us to make sure that we’re writing the highest quality code possible.
Sure, some of these may be in the form of something like coding standards, but those are really more rules than they are elements of writing high quality code (though I don’t think they should be left out of the discussion – just left out at this time 🙃).
Back to the tools in question: What are some tools that help write high quality WordPress code? I’m going to share a few of my favorites and them I’m going to talk about how we can run them all against a code base.
First, let’s take a look at static analysis with PHPStan.
This is something I’ve been doing for a while now, and it’s something that I’ve found useful both for my personal and professional life.
And I don’t want to try to come up with some other reason for doing this so I’ll quote my previous post (because quoting yourself isn’t narcissistic or anything, is it?):
Every time I end up taking time off of social media in general, I never regret it. At the same time, I also find new things I want to do during that time.
But one of the things I like do during this post other than share that I am doing it (because I see this site as the primary place to keep up with me – not Twitter, not Instagram, not AIM, not ICQ), I like also to cover what I plan to do.