From 2a6000a646de34e015e4820ed9d236a6c7f7b413 Mon Sep 17 00:00:00 2001 From: Martin Keckeis Date: Tue, 17 Feb 2015 12:57:38 +0100 Subject: [PATCH] Some update (see comment) - remove ZF1 cs (since ZF2using now psr) - php-cs-fixer is not "owned" by fabpot anymore --- _posts/02-01-01-Code-Style-Guide.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/_posts/02-01-01-Code-Style-Guide.md b/_posts/02-01-01-Code-Style-Guide.md index 27d1657..da55933 100644 --- a/_posts/02-01-01-Code-Style-Guide.md +++ b/_posts/02-01-01-Code-Style-Guide.md @@ -24,17 +24,13 @@ applications that implement the components can have consistency even when workin * [Read about PSR-2][psr2] * [Read about PSR-4][psr4] * [Read about PEAR Coding Standards][pear-cs] -* [Read about Zend Coding Standards][zend-cs] * [Read about Symfony Coding Standards][symfony-cs] You can use [PHP_CodeSniffer][phpcs] to check code against any one of these recommendations, and plugins for text editors like [Sublime Text 2][st-cs] to be given real time feedback. -You can fix the code layout automatically by using one of the two possible tools. One is Fabien Potencier's -[PHP Coding Standards Fixer][phpcsfixer] which has a very well tested codebase. It is bigger and slower, but very -stable and used by some huge projects like Magento and Symfony. Another option is [php.tools][phptools], which is made -popular by the [sublime-phpfmt][sublime-phpfmt] editor plugin. While being newer, it makes great improvements in -performance, meaning real-time editor fixing is more fluid. +You can fix the code layout automatically by using one of the two following tools. One is the [PHP Coding Standards Fixer][phpcsfixer] which has a very well tested codebase. +Another option is [php.tools][phptools], which is made popular by the [sublime-phpfmt][sublime-phpfmt] editor plugin. While being newer, it makes great improvements in performance, meaning real-time editor fixing is more fluid. English is preferred for all symbol names and code infrastructure. Comments may be written in any language easily readable by all current and future parties who may be working on the codebase. @@ -46,7 +42,6 @@ readable by all current and future parties who may be working on the codebase. [psr2]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md [psr4]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4-autoloader.md [pear-cs]: http://pear.php.net/manual/en/standards.php -[zend-cs]: http://framework.zend.com/manual/1.12/en/coding-standard.html [symfony-cs]: http://symfony.com/doc/current/contributing/code/standards.html [phpcs]: http://pear.php.net/package/PHP_CodeSniffer/ [st-cs]: https://github.com/benmatselby/sublime-phpcs