info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-08 06:56:33 +02:00
Code Issues Projects Releases Wiki Activity

Remove deprecated PSR0 from code style section

Browse Source
This commit is contained in:
Josh Lockhart
2018-06-19 13:04:28 -04:00
parent 2e51866e73
commit 4fd12a4742
1 changed files with 9 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
_posts/02-01-01-Code-Style-Guide.md
View File

@@ -10,7 +10,7 @@ PHP developers to choose several of these and combine them into a single project
their projects. their projects.
The [Framework Interop Group][fig] has proposed and approved a series of style recommendations. Not all of them related The [Framework Interop Group][fig] has proposed and approved a series of style recommendations. Not all of them related
to code-style, but those that do are [PSR-0][psr0], [PSR-1][psr1], [PSR-2][psr2] and [PSR-4][psr4]. These to code-style, but those that do are [PSR-1][psr1], [PSR-2][psr2] and [PSR-4][psr4]. These
recommendations are merely a set of rules that many projects like Drupal, Zend, Symfony, Laravel, CakePHP, phpBB, AWS SDK, recommendations are merely a set of rules that many projects like Drupal, Zend, Symfony, Laravel, CakePHP, phpBB, AWS SDK,
FuelPHP, Lithium, etc are adopting. You can use them for your own projects, or continue to use your own FuelPHP, Lithium, etc are adopting. You can use them for your own projects, or continue to use your own
personal style. personal style.
@@ -19,7 +19,6 @@ Ideally, you should write PHP code that adheres to a known standard. This could
of the coding standards made by PEAR or Zend. This means other developers can easily read and work with your code, and of the coding standards made by PEAR or Zend. This means other developers can easily read and work with your code, and
applications that implement the components can have consistency even when working with lots of third-party code. applications that implement the components can have consistency even when working with lots of third-party code.
* [Read about PSR-0][psr0]
* [Read about PSR-1][psr1] * [Read about PSR-1][psr1]
* [Read about PSR-2][psr2] * [Read about PSR-2][psr2]
* [Read about PSR-4][psr4] * [Read about PSR-4][psr4]
@@ -57,14 +56,13 @@ English is preferred for all symbol names and code infrastructure. Comments may
readable by all current and future parties who may be working on the codebase. readable by all current and future parties who may be working on the codebase.
[fig]: http://www.php-fig.org/ [fig]: https://www.php-fig.org/
[psr0]: http://www.php-fig.org/psr/psr-0/ [psr1]: https://www.php-fig.org/psr/psr-1/
[psr1]: http://www.php-fig.org/psr/psr-1/ [psr2]: https://www.php-fig.org/psr/psr-2/
[psr2]: http://www.php-fig.org/psr/psr-2/ [psr4]: https://www.php-fig.org/psr/psr-4/
[psr4]: http://www.php-fig.org/psr/psr-4/ [pear-cs]: https://pear.php.net/manual/en/standards.php
[pear-cs]: http://pear.php.net/manual/en/standards.php [symfony-cs]: https://symfony.com/doc/current/contributing/code/standards.html
[symfony-cs]: http://symfony.com/doc/current/contributing/code/standards.html [phpcs]: https://pear.php.net/package/PHP_CodeSniffer/
[phpcs]: http://pear.php.net/package/PHP_CodeSniffer/
[phpcbf]: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Fixing-Errors-Automatically [phpcbf]: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Fixing-Errors-Automatically
[st-cs]: https://github.com/benmatselby/sublime-phpcs [st-cs]: https://github.com/benmatselby/sublime-phpcs
[phpcsfixer]: http://cs.sensiolabs.org/ [phpcsfixer]: https://cs.sensiolabs.org/