/protected/vendor/fabpot/php-cs-fixer/COOKBOOK-FIXERS.md
Markdown | 466 lines | 375 code | 91 blank | 0 comment | 0 complexity | d659e77a6fb5ce5117024c42083eff20 MD5 | raw file
- Cookbook - Making a new Fixer for PHP CS Fixer
- ==============================================
- You want to make a new fixer to PHP CS Fixer and do not know how to
- start. Follow this document and you will be able to do it.
- ## Background
- In order to be able to create a new fixer, you need some background.
- PHP CS Fixer is a transcompiler which takes valid PHP code and pretty
- print valid PHP code. It does all transformations in multiple passes,
- a.k.a., multi-pass compiler.
- Therefore, a new fixer is meant to be ideally
- [idempotent](http://en.wikipedia.org/wiki/Idempotence#Computer_science_meaning),
- or at least atomic in its actions. More on this later.
- All contributions go through a code review process. Do not feel
- discouraged - it is meant only to give more people more chance to
- contribute, and to detect bugs ([Linus'
- Law](http://en.wikipedia.org/wiki/Linus%27s_Law)).
- If possible, try to get acquainted with the public interface for the
- [Symfony/CS/Tokenizer/Tokens.php](Symfony/CS/Tokenizer/Tokens.php)
- and [Symfony/CS/Tokenizer/Token.php](Symfony/CS/Tokenizer/Token.php)
- classes.
- ## Assumptions
- * You are familiar with Test Driven Development.
- * Forked FriendsOfPHP/PHP-CS-Fixer into your own Github Account.
- * Cloned your forked repository locally.
- * Downloaded PHP CS Fixer and have executed `php composer.phar
- install`.
- * You have read [`CONTRIBUTING.md`](CONTRIBUTING.md)
- ## Step by step
- For this step-by-step, we are going to create a simple fixer that
- removes all comments of the code that are preceded by ';' (semicolon).
- We are calling it `remove_comments` (code name), or,
- `RemoveCommentsFixer` (class name).
- ### Step 1 - Creating files
- Create a new file in
- `PHP-CS-Fixer/Symfony/CS/Fixer/Contrib/RemoveCommentsFixer.php`.
- Put this content inside:
- ```php
- <?php
- /*
- * This file is part of the PHP CS utility.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
- namespace Symfony\CS\Fixer\Contrib;
- use Symfony\CS\AbstractFixer;
- use Symfony\CS\Tokenizer\Tokens;
- /**
- * @author Your name <your@email.com>
- */
- final class RemoveCommentsFixer extends AbstractFixer
- {
- }
- ```
- Note how the class and file name match. Also keep in mind that all
- fixers must implement `FixerInterface`. In this case, the fixer is
- inheriting from `AbstractFixer`, which fulfills the interface with some
- default behavior.
- Now let us create the test file at
- `Symfony/CS/Tests/Fixer/Contrib/RemoveCommentsFixerTest.php` . Put this
- content inside:
- ```php
- <?php
- /*
- * This file is part of the PHP CS utility.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
- namespace Symfony\CS\Tests\Fixer\Contrib;
- use Symfony\CS\Tests\Fixer\AbstractFixerTestBase;
- /**
- * @author Your name <your@email.com>
- *
- * @internal
- */
- final class RemoveCommentsFixerTest extends AbstractFixerTestBase
- {
- /**
- * @dataProvider provideFixCases
- */
- public function testFix($expected, $input = null)
- {
- $this->makeTest($expected, $input);
- }
- public function provideFixCases()
- {
- return array();
- }
- }
- ```
- The files are created, one thing is still missing though: we need to
- update the README.md. Fortunately, PHP CS Fixer can help you here.
- Execute the following command in your command shell:
- `# php php-cs-fixer readme > README.rst`
- ### Step 2 - Using tests to define fixers behavior
- Now that the files are created, you can start writing test to define the
- behavior of the fixer. You have to do it in two ways: first, ensuring
- the fixer changes what it should be changing; second, ensuring that
- fixer does not change what is not supposed to change. Thus:
- #### Keeping things as they are:
- `Symfony/CS/Tests/Fixer/Contrib/RemoveCommentsFixerTest.php`@provideFixCases:
- ```php
- ...
- public function provideFixCases()
- {
- return array(
- array('<?php echo "This should not be changed";') // Each sub-array is a test
- );
- }
- ...
- ```
- #### Ensuring things change:
- `Symfony/CS/Tests/Fixer/Contrib/RemoveCommentsFixerTest.php`@provideFixCases:
- ```php
- ...
- public function provideFixCases()
- {
- return array(
- array(
- '<?php echo "This should be changed"; ', // This is expected output
- '<?php echo "This should be changed"; /* Comment */', // This is input
- )
- );
- }
- ...
- ```
- Note that expected outputs are **always** tested alone to ensure your fixer will not change it.
- We want to have a failing test to start with, so the test file now looks
- like:
- `Symfony/CS/Tests/Fixer/Contrib/RemoveCommentsFixerTest.php`
- ```php
- <?php
- /*
- * This file is part of the PHP CS utility.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
- namespace Symfony\CS\Tests\Fixer\Contrib;
- use Symfony\CS\Tests\Fixer\AbstractFixerTestBase;
- /**
- * @author Your name <your@email.com>
- *
- * @internal
- */
- final class RemoveCommentsFixerTest extends AbstractFixerTestBase
- {
- /**
- * @dataProvider provideFixCases
- */
- public function testFix($expected, $input = null)
- {
- $this->makeTest($expected, $input);
- }
- public function provideFixCases()
- {
- return array(
- array(
- '<?php echo "This should be changed"; ', // This is expected output
- '<?php echo "This should be changed"; /* Comment */', // This is input
- )
- );
- }
- }
- ```
- ### Step 3 - Implement your solution
- You have defined the behavior of your fixer in tests. Now it is time to
- implement it.
- We need first to create one method to describe what this fixer does:
- `Symfony/CS/Fixer/Contrib/RemoveCommentsFixer.php`:
- ```php
- final class RemoveCommentsFixer extends AbstractFixer
- {
- ...
- /**
- * {@inheritdoc}
- */
- public function getDescription()
- {
- return 'Removes all comments of the code that are preceded by ";" (semicolon).'; // Trailing dot is important. We thrive to use English grammar properly.
- }
- }
- ```
- For now, let us just make a fixer that applies no modification:
- `Symfony/CS/Fixer/Contrib/RemoveCommentsFixer.php`:
- ```php
- final class RemoveCommentsFixer extends AbstractFixer
- {
- /**
- * {@inheritdoc}
- */
- public function fix(\SplFileInfo $file, $content)
- {
- $tokens = Tokens::fromCode($content);
- return $tokens->generateCode();
- }
- }
- ```
- Run `vendor/bin/phpunit`. You are going to see that the tests fails.
- ### Break
- Now we have pretty much a cradle to work with. A file with a failing
- test, and the fixer, that for now does not do anything.
- How do fixers work? In the PHP CS Fixer, they work by iterating through
- pieces of codes (each being a Token), and inspecting what exists before
- and after that bit and making a decision, usually:
- * Adding code.
- * Modifying code.
- * Deleting code.
- * Ignoring code.
- In our case, we want to find all comments, and foreach (pun intended)
- one of them check if they are preceded by a semicolon symbol.
- Now you need to do some reading, because all these symbols obey a list
- defined by the PHP compiler. It is the ["List of Parser
- Tokens"](http://php.net/manual/en/tokens.php).
- Internally, PHP CS Fixer transforms some of PHP native tokens into custom
- tokens through the use of [Transfomers](Symfony/CS/Tokenizer/Transformer),
- they aim to help you reason about the changes you may want to do in the
- fixers.
- So we can get to move forward, humor me in believing that comments have
- one symbol name: `T_COMMENT`.
- ### Step 3 - Implement your solution - continuation.
- We do not want all symbols to be analysed. Only `T_COMMENT`. So let us
- iterate the token(s) we are interested in.
- `Symfony/CS/Fixer/Contrib/RemoveCommentsFixer.php`:
- ```php
- final class RemoveCommentsFixer extends AbstractFixer
- {
- /**
- * {@inheritdoc}
- */
- public function fix(\SplFileInfo $file, $content)
- {
- $tokens = Tokens::fromCode($content);
- $foundComments = $tokens->findGivenKind(T_COMMENT);
- foreach($foundComments as $index => $token){
- }
- return $tokens->generateCode();
- }
- }
- ```
- OK, now for each `T_COMMENT`, all we need to do is check if the previous
- token is a semicolon.
- `Symfony/CS/Fixer/Contrib/RemoveCommentsFixer.php`:
- ```php
- final class RemoveCommentsFixer extends AbstractFixer
- {
- /**
- * {@inheritdoc}
- */
- public function fix(\SplFileInfo $file, $content)
- {
- $tokens = Tokens::fromCode($content);
- $foundComments = $tokens->findGivenKind(T_COMMENT);
- foreach($foundComments as $index => $token){
- $prevTokenIndex = $tokens->getPrevMeaningfulToken($index);
- $prevToken = $tokens[$prevTokenIndex];
- if($prevToken->equals(';')){
- $token->clear();
- }
- }
- return $tokens->generateCode();
- }
- }
- ```
- So the fixer in the end looks like this:
- ```php
- <?php
- /*
- * This file is part of the PHP CS utility.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- *
- */
- namespace Symfony\CS\Fixer\Contrib;
- use Symfony\CS\AbstractFixer;
- use Symfony\CS\Tokenizer\Tokens;
- /**
- * @author Your name <your@email.com>
- */
- final class RemoveCommentsFixer extends AbstractFixer {
- /**
- * {@inheritdoc}
- */
- public function fix(\SplFileInfo $file, $content) {
- $tokens = Tokens::fromCode($content);
- $foundComments = $tokens->findGivenKind(T_COMMENT);
- foreach ($foundComments as $index => $token) {
- $prevTokenIndex = $tokens->getPrevMeaningfulToken($index);
- $prevToken = $tokens[$prevTokenIndex];
- if ($prevToken->equals(';')) {
- $token->clear();
- }
- }
- return $tokens->generateCode();
- }
- /**
- * {@inheritdoc}
- */
- public function getDescription() {
- return 'Removes all comments of the code that are preceded by ";" (semicolon).';// Trailing dot is important. We thrive to use English grammar properly.
- }
- }
- ```
- ### Step 4 - Format, Commit, PR.
- Note that so far, we have not coded adhering to PSR-1/2. This is done on
- purpose. For every commit you make, you must use PHP CS Fixer to fix
- itself. Thus, on the command line call:
- `$ php php-cs-fixer fix`
- This will fix all the coding style mistakes.
- After the final CS fix, you are ready to commit. Do it.
- Now, go to Github and open a Pull Request.
- ### Step 5 - Peer review: it is all about code and community building.
- Congratulations, you have made your first fixer. Be proud. Your work
- will be reviewed carefully by PHP CS Fixer community.
- The review usually flows like this:
- 1. People will check your code for common mistakes and logical
- caveats. Usually, the person building a fixer is blind about some
- behavior mistakes of fixers. Expect to write few more tests to cater for
- the reviews.
- 2. People will discuss the relevance of your fixer. If it is
- something that goes along with Symfony style standards, or PSR-1/PSR-2
- standards, they will ask you to move from Symfony/CS/Fixers/Contrib to
- Symfony/CS/Fixers/{Symfony, PSR2, etc}.
- 3. People will also discuss whether your fixer is idempotent or not.
- If they understand that your fixer must always run before or after a
- certain fixer, they will ask you to override a method named
- `getPriority()`. Do not be afraid of asking the reviewer for help on how
- to do it.
- 4. People may ask you to rebase your code to unify commits or to get
- rid of merge commits.
- 5. Go to 1 until no actions are needed anymore.
- Your fixer will be incorporated in the next release.
- # Congratulations! You have done it.
- ## Q&A
- #### Why is not my PR merged yet?
- PHP CS Fixer is used by many people, that expect it to be stable. So
- sometimes, few PR are delayed a bit so to avoid cluttering at @dev
- channel on composer.
- Other possibility is that reviewers are giving time to other members of
- PHP CS Fixer community to partake on the review debates of your fixer.
- In any case, we care a lot about what you do and we want to see it being
- part of the application as soon as possible.
- #### May I use short arrays (`$a = []`)?
- No. Short arrays were introduced in PHP 5.4 and PHP CS Fixer still
- supports PHP 5.3.6.
- #### Why are you steering me to create my fixer at CONTRIB_LEVEL ?
- CONTRIB_LEVEL is the most lax level - and it is far more likely to have
- your fixer accepted at CONTRIB_LEVEL and later changed to SYMFOMY_LEVEL
- or PSR2_LEVEL; than the other way around.
- If you make your contribution directly at PSR2_LEVEL, eventually the
- relevance debate will take place and your fixer might be pushed to
- CONTRIB_LEVEL.
- #### Why am I asked to use `getPrevMeaningfulToken()` instead of `getPrevNonWhitespace()`?
- The main difference is that `getPrevNonWhitespace()` ignores only
- whitespaces (`T_WHITESPACE`), while `getPrevMeaningfulToken()` ignores
- whitespaces and comments. And usually that is what you want. For
- example:
- ```php
- $a->/*comment*/func();
- ```
- If you are inspecting `func()`, and you want to check whether this is
- part of an object, if you use `getPrevNonWhitespace()` you are going to
- get `/*comment*/`, which might belie your test. On the other hand, if
- you use `getPrevMeaningfulToken()`, no matter if you have got a comment
- or a whitespace, the returned token will always be `->`.