From 9c3a17d0244b683dcf4acec3092d383def6ec607 Mon Sep 17 00:00:00 2001 From: William Turrell Date: Wed, 28 Sep 2016 21:56:25 +0100 Subject: [PATCH] Code Style Guide - project list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Be bolder (some -> many) - How can we not have Laravel… --- _posts/02-01-01-Code-Style-Guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/02-01-01-Code-Style-Guide.md b/_posts/02-01-01-Code-Style-Guide.md index 9182cee..3365509 100644 --- a/_posts/02-01-01-Code-Style-Guide.md +++ b/_posts/02-01-01-Code-Style-Guide.md @@ -11,8 +11,8 @@ their projects. 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 -recommendations are merely a set of rules that some projects like Drupal, Zend, Symfony, CakePHP, phpBB, AWS SDK, -FuelPHP, Lithium, etc are starting to adopt. You can use them for your own projects, or continue to use your own +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 personal style. Ideally you should write PHP code that adheres to a known standard. This could be any combination of PSRs, or one