Wallogit.com
2017 © Pedro Peláez
Development standards by and for TreeHouse employees
This repository provides documentation and tools to help comply with our code standards., (*1)
We mostly adhere to the Symfony code style, but each project can define its own rules. What's more important than specific rules, is that everyone applies them, consistently. That's what this repository aims to help with., (*2)
To install in a project, add this as a dev dependency:, (*3)
composer require --dev treehouselabs/standards
Copy the distributed .php_cs file, modify where needed:, (*4)
cp vendor/treehouselabs/standards/.php_cs .
NOTE: Make sure that .php_cs.cache is in .gitignore!, (*5)
vendor/ .php_cs.cache composer.lock
When the fixer is run as a Travis script, builds fail when there is a CS
violation. Add this to .travis.yml:, (*6)
script: - bin/php-cs-fixer fix --config=.php_cs --verbose --diff --dry-run
For increased performance, make sure to cache the fixer's cache dir:, (*7)
cache:
directories:
- $HOME/.php-cs-fixer
There are multiple ways to integrate CS in your workflow. Here are some methods that we use:, (*8)
Not the easiest way, but if it suits you, adopt the code style, and write it that way. No fixes needed!, (*9)
At any time before committing, run the fixer manually:, (*10)
./bin/php-cs-fixer fix -v
This can also be done using a plugin for your editor of choice., (*11)
The repository ships with a git pre-commit hook that automatically fixes your code before committing it. Be careful however since this can modify code without you seeing it., (*12)
cp vendor/treehouselabs/standards/hooks/pre-commit .git/pre-commit chmod +x .git/pre-commit
Of course if you prefer a different method, that's cool. Whatever works. Again, the important thing is that it's applied consistently., (*13)
Development standards by and for TreeHouse employees
MIT
Development standards by and for TreeHouse employees
MIT
Development standards by and for TreeHouse employees