Meetings

We have a project meeting twice a month on Tuesday at 17:00 UTC in the #themereview channel on Slack. Second Tuesday in the month is open floor and the fourth Tuesday is with a fixed agenda. Tuesday at 17:00 UTC.

We also went through the open issues and closed some, while others were labeled appropriately. On some issues we need a second opinion or more information to crystallize what actually needs to be sniffed for, so be sure to leave a comment.

As development in the WordPress Coding Standards project has been plenty active in the past year, several new WPCS sniffs were identified which we can use for the TRTCS ruleset, so those will be added in the coming weeks.

The authors of the pull requests that need to be updated were notified, and we decided to give them until Monday to respond whether they would like to continue work on the PR or not. After that Juliette will probably update them since she has the most knowledge about writing sniffs.

The way people can contribute, besides writing sniffs (which can be a bit daunting to someone who never wrote one), is to post code examples in the issues or in the pull requests that would correspond to the issue/sniff in question. This really helps with unit testing the sniff as clear specifications make writing the sniff that much easier.

As for Theme sniffer, I’ve written a way to circumvent a possible bottleneck of code sniffer – minified files. This will need to be tested of course. In addition to that, the way files are sniffed will have to be changed – sniffing in batch, instead of the current way of sniffing files one by one. I’ll try to fix that as soon as possible so that you can test it and report possible issues.

Sorry for not answering sooner, had a lot going on. phpcs has a run() method in the Runner class, that will process all files, just like when you go to the terminal and hit phpcs . 🙂
I’m just starting to work on this, hopefully, I’ll have something to show soon.