In this post, I’ll wrap up what I began to share yesterday: Using the tools and libraries I’ve shared in conjunction with Composer to sniff your commits during development before the code hits the repository.
Ideally, you’re always going to want to see something like this in your terminal whenever you commit your code:
But that’s not always the case. As with most things, though, the more you practice, the more you’ll get used to writing code that will automatically pass the various sniffs put in place through the different rules (and their customizations).
Before doing that, though, you’ve got to get GrumPHP configured in your repository.
Continue reading “Configuring Composer for WordPress, Part 2 The final post in a series that shows how to configure Composer to use code examined in a previous series for writing high-quality code.“
Okay, so after talking through all of the various libraries that can help improve the code quality of your work, it still raises a question:
How do we get these projects working against our code base?
In short, it requires Composer. If you’ve never used it, I’ve written briefly about it before, but I intend to provide the basics of what you need to get started using it and the aforementioned libraries in your work.
In both this post and the next, I’ll share how to set up everything locally in the most basic form and then how it integrates with Git so you can start using it in your day-to-day.
Continue reading “Configuring Composer for WordPress, Part 1 The first in a series that shows how to configure Composer to use code examined in a previous series for writing high-quality code.“