Download the PHP package bit3/php-coding-standard without Composer
On this page you can find all versions of the php package bit3/php-coding-standard. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download bit3/php-coding-standard
More information about bit3/php-coding-standard
Files in bit3/php-coding-standard
Package php-coding-standard
Short Description bit3 PHP coding standards
License BSD-3-Clause GPL-2.0+
Homepage http://bit3.de
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package php-coding-standard
bit3 coding standards
These are our coding standards.
This coding standard based on the great TYPO3 coding standard, see http://forge.typo3.org/projects/team-php_codesniffer/wiki/Using_the_TYPO3_Coding_Standard
Philosophy
Our philosophy: Write fast readable and comprehensible code. Don't be shy to write more lines, if it makes each line more atomic.
What is the benefit of atomic lines? When each line is full atomic (only contains one operation), the order of lines reflect the execution order of the commands.
When you have a complex line like this:
How is the order of execution? What do this code? You can understand if you analyse the line, but its hard to do. Simplified this is the execution order of the operations:
If you want to understand what this code do, you have to understand the execution order of the operations and the meaning of each operation. If you write this in a more atomic style, you make it easier to understand, for others and yourself if you nod touch the code a long time!
Compare against this, it is exactly the same code:
As you can see, this snippet more reflect the execution order and it is much easier to understand what it do.
Usage
Install the coding standards via composer:
After updating dependencies, copy the example ant build file from vendor/bit3/php-coding-standard/example/build.xml into your project.
If your sources are not in src/, change the path to your sources in the build file.
Hint: If you not use phpunit, remove the phpunit target from build file.
You can run the tests by invoke ant phpmd and ant phpcs.
Running ant or ant test will run all test targets.
Hint: To run all testes, even if one fail, use ant -keep-going.
Definitions
- long line means a line that is longer than 60 characters.
- No line should be longer than 100 characters.
- No line must be longer than 120 characters.
Files
No file must contain more than one class, interface or function.
The file name must the same (including case) as the class, interface or function named defined in it.
Without any prefix (e.g. class.) or suffix (e.g. .inc), expect the the file type extension .php.
Runner scripts, should contain a runner class, containing a run method.
Example index.php:
Hint: Runner classes must not be in pascal-case, but must match the file name.
Second example ajax.php
Whitespaces
Do not use SPACE for indention. Use TAB.
Add spaces to split operators:
- assignment:
$variable = 'value' - parameters:
func($a, $b, $c) - arrays:
array('foo' => 'bar', 'bar' => 'foo') - comments:
// commentor* multiline comment
Class and function declaration
Place opening brace { on new line for all non-control-structures like class or function declaration.
Place extends and implements on new line and indent one time.
Don't add a space before opening bracked ( in function declarations or calls.
Naming
Use pascal-case class names.
Use camel-case method names.
Control structures
Place opening brace { on same line for all control-structures.
Add newline after closing brace }, even the control-structure continues.
Why putting the else on a new line?
It's simple, first it is the beginning of a new block. Second it is easier to make comments that describe the conditions.
Long and multiline conditions
If control-structure condition gets to long, place closing bracket and opening brace ) { in a separate line and place condition in separate line.
Don't forget the whitespace before opening bracket (.
Ternary operator
When using ternary operator, you should put then and else part in separate lines and indent one time if line gets longer.
Ternary operator should only be used for simple left/right decisions. Do not use in combination with complex conditions or logic.
Function/Method calls
In function/method calls use space to split parameters, but do not add space before opening bracket (.
When parameter list gets long, make it multiline and put every parameter on a singleline.
Also put the closing bracket ) on a singleline.
When chain method calls, put each method call in separate line if it make sense or the line gets to long.
Variables
Initialisation
Make complex array initialisations multiline and put every element in single line.
Naming
Use camel-case variable names. Use significant variable names instead type prefix.
Logic
Keep every line as simple as possible, do not combine to many operations in one line. Use readable control structures if needed, even you write a lot more lines!
Don't use logic in function call parameters.
Use function or method chaining with caution, but keep it as simple as possible.
