digisavvy / some-like-it-neat

A WordPress Theme Using _s, Bourbon + Neat and Theme Hook Alliance
GNU General Public License v2.0
276 stars 61 forks source link

Double Checking What PHPCS is looking in #57

Closed digisavvy closed 9 years ago

digisavvy commented 9 years ago

Just need to verify we're looking at php files in root theme directory, page-templates and that's really it; I don't think we should be checking anything else.

Thoughts?

desaiuditd commented 9 years ago

This is the filter that I've put on phpcs.

phpcs --ignore='node_modules/*,vendor/*,*-min.css,assets/js/vendor/*,assets/bower_components/*,assets/css/*,*-min.js,assets/js/production.js' --standard='WordPress-Core' .

So basically, this will skip following folders/files and scan rest of all.

I'm open to change this logic.

Also, in master branch there are a few conflicting files which are causing phpcs errors. I don't understand their purpose. I was not sure whether to keep them or not. Below:

Why do we need an empty php file under these folders ?

digisavvy commented 9 years ago

Thanks so much. The files you noted are there as a "flimsy security" deterrent to keep people from directly accessing the directory.. I can remove them.

digisavvy commented 9 years ago

Okay, I've removed those files; Header.php is still throwing a few errors and I'm not sure how to resolve.

Also took your advice and consolidated branches down to master and development and used tags for all other release points

desaiuditd commented 9 years ago

That's cool. :+1: I've pushed one commit. And phpcs log is clean now.

screenshot from 2015-02-12 19 43 27

Please confirm. :smiley:

digisavvy commented 9 years ago

Boom! Looks good from here, too! Thanks. =)