dependabot-composer 0.119.0.beta1 → 0.119.0

data/helpers/vendor/friendsofphp/php-cs-fixer/UPGRADE.md

@@ -1,184 +0,0 @@
-UPGRADE GUIDE FROM 1.x to 2.0
-=============================
-
-This is guide for upgrade from version 1.x to 2.0 for using the CLI tool.
-
-Rules and sets
---------------
-To configure which fixers should be used you must now set rules and sets instead of fixers and level. This affects both configuration file and CLI arguments.
-
-Default ruleset was changed from Symfony standard to more generic PSR2. You can still use Symfony standard, which in fact extends PSR2.
-
-The term of risky fixers was introduced. Risky fixer is a fixer that may change the meaning of code (like `StrictComparisonFixer` fixer, which will change `==` into `===`). No rules that are followed by risky fixers are run by default. You need to explicitly permit risky fixers to run them.
-
-Default configuration changes
-----------------------------
-By default, PSR2 rules are used instead of Symfony rules.
-Files that will be fixed are php/phpt/twig instead of php/twig/xml/yml.
-Finally, the caching mechanism is enabled by default.
-
-CLI options
------------
-
-| 1.x             | 2.0             | Description                                                                    | Note                            |
-| --------------- | --------------- | ------------------------------------------------------------------------------ | ------------------------------- |
-|                 | --allow-risky   | Are risky fixers allowed                                                       |                                 |
-|                 | --cache-file    | The path to the cache file                                                     | option was added                |
-| --config        |                 | Config class codename                                                          | option was removed              |
-| --config-file   | --config        | The path to a .php_cs file                                                     | option was renamed              |
-| --diff          | --diff          | Show diff                                                                      |                                 |
-| --dry-run       | --dry-run       | Run in dry-run mode                                                            |                                 |
-| --fixers        |                 | Coding standard fixers                                                         | option was removed, see --rules |
-| --format        | --format        | Choose format                                                                  |                                 |
-| --level         |                 | Coding standard level                                                          | option was removed, see --rules |
-|                 | --path-mode     | Should the finder from config be<br/>overridden or intersected with `path` arg | option was added                |
-|                 | --rules         | Rules to be used                                                               | option was added                |
-|                 | --using-cache   | Does cache should be used                                                      | option was added                |
-
-
-CLI argument
-------------
-
-On 2.x line `path` argument is an array, so you may pass multiple paths.
-
-Intersection path mode makes the `path` argument a mask for finder you have defined in your configuration file.
-Only files pointed by both finder and CLI `path` argument will be fixed.
-
-Exit codes
-----------
-
-Exit codes for `fix` command have been changed and are build using the following bit flags:
-
-| 1.x bit | 2.0 bit | Description                                                 | Note                                                             |
-| -------:| -------:| ----------------------------------------------------------- | ---------------------------------------------------------------- |
-| 0       | 0       | OK                                                          |                                                                  |
-| 1       | 1       | General error (or PHP/HHVM minimal requirement not matched) | no longer used for other states, never combined with other flags |
-|         | 4       | Some files have invalid syntax                              | flag was added, works only in dry-run mode                       |
-|         | 8       | Some files need fixing                                      | flag was added, works only in dry-run mode                       |
-| 16      | 16      | Configuration error of the application                      |                                                                  |
-| 32      | 32      | Configuration error of a Fixer                              |                                                                  |
-|         | 64      | Exception within the application                            | flag was added                                                   |
-
-Namespace
----------
-`Symfony\CS` namespace was renamed into `PhpCsFixer`.
-
-Config file
------------
-From now you can create new configuration file: `.php_cs.dist`. This file is used if no `.php_cs` file was found. It is recommended to create `.php_cs.dist` file attached in your repository and add `.php_cs` file to `.gitignore` for allowing your contributors to have theirs own configuration file.
-
-Config and Finder classes
--------------------------
-All off `Symfony\CS\Config\*` and `Symfony\CS\Finder\*` classes have been removed, instead use `PhpCsFixer\Config` and `PhpCsFixer\Finder`.
-
-For that reason you can not set config class by `--config` CLI argument, from now it is used to set configuration file. Therefor the `--config-file` CLI argument is no longer available.
-
-Renamed rules
--------------
-
-Old name | New name | Note
--------- | -------- | ----
-align_double_arrow                             | binary_operator_spaces                            | use configuration ['align_double_arrow' => true]
-align_equals                                   | binary_operator_spaces                            | use configuration ['align_equals' => true]
-array_element_no_space_before_comma            | no_whitespace_before_comma_in_array
-array_element_white_space_after_comma          | whitespace_after_comma_in_array
-blankline_after_open_tag                       | blank_line_after_opening_tag
-concat_with_spaces                             | concat_space                                      | use configuration ['spacing' => 'one']
-concat_without_spaces                          | concat_space                                      | use configuration ['spacing' => 'none']
-double_arrow_multiline_whitespaces             | no_multiline_whitespace_around_double_arrow
-duplicate_semicolon                            | no_empty_statement                                | new one fixes more cases
-empty_return                                   | simplified_null_return
-echo_to_print                                  | no_mixed_echo_print                               | use configuration ['use' => 'print']
-eof_ending                                     | single_blank_line_at_eof
-extra_empty_lines                              | no_extra_consecutive_blank_lines
-function_call_space                            | no_spaces_after_function_name
-general_phpdoc_annotation_rename               | phpdoc_no_alias_tag                               | use configuration ['property-read' => 'property', 'property-write' => 'property']
-indentation                                    | indentation_type
-join_function                                  | no_alias_functions                                | new one fixes more aliases
-line_after_namespace                           | blank_line_after_namespace
-linefeed                                       | line_ending                                       | whitespaces type aware
-list_commas                                    | no_trailing_comma_in_list_call
-logical_not_operators_with_spaces              | not_operator_with_space
-logical_not_operators_with_successor_space     | not_operator_with_successor_space
-long_array_syntax                              | array_syntax                                      | use configuration ['syntax' => 'long']
-method_argument_default_value                  | no_unreachable_default_argument_value
-multiline_array_trailing_comma                 | trailing_comma_in_multiline_array
-multiline_spaces_before_semicolon              | no_multiline_whitespace_before_semicolons
-multiple_use                                   | single_import_per_statement
-namespace_no_leading_whitespace                | no_leading_namespace_whitespace
-newline_after_open_tag                         | linebreak_after_opening_tag
-no_empty_lines_after_phpdocs                   | no_blank_lines_after_phpdoc
-object_operator                                | object_operator_without_whitespace
-operators_spaces                               | binary_operator_spaces
-ordered_use                                    | ordered_imports
-parenthesis                                    | no_spaces_inside_parenthesis
-php4_constructor                               | no_php4_constructor
-php_closing_tag                                | no_closing_tag
-phpdoc_params                                  | phpdoc_align
-phpdoc_property                                | phpdoc_no_alias_tag                               | use configuration ['type' => 'var']
-phpdoc_short_description                       | phpdoc_summary
-phpdoc_type_to_var                             | phpdoc_no_alias_tag                               | use configuration ['type' => 'var']
-phpdoc_var_to_type                             | phpdoc_no_alias_tag                               | use configuration ['var' => 'type']
-print_to_echo                                  | no_mixed_echo_print                               | use configuration ['use' => 'echo']
-remove_leading_slash_use                       | no_leading_import_slash
-remove_lines_between_uses                      | no_extra_consecutive_blank_lines                  | use configuration ['use']
-return                                         | blank_line_before_return
-short_array_syntax                             | array_syntax                                      | use configuration ['syntax' => 'short']
-short_bool_cast                                | no_short_bool_cast
-short_echo_tag                                 | no_short_echo_tag
-short_tag                                      | full_opening_tag
-single_array_no_trailing_comma                 | no_trailing_comma_in_singleline_array
-spaces_after_semicolon                         | space_after_semicolon
-spaces_before_semicolon                        | no_singleline_whitespace_before_semicolons
-spaces_cast                                    | cast_spaces
-standardize_not_equal                          | standardize_not_equals
-strict                                         | strict_comparison
-ternary_spaces                                 | ternary_operator_spaces
-trailing_spaces                                | no_trailing_whitespace
-unalign_double_arrow                           | binary_operator_spaces                            | use configuration ['align_double_arrow' => false]
-unalign_equals                                 | binary_operator_spaces                            | use configuration ['align_equals' => false]
-unary_operators_spaces                         | unary_operator_spaces
-unneeded_control_parentheses                   | no_unneeded_control_parentheses
-unused_use                                     | no_unused_imports
-visibility                                     | visibility_required
-whitespacy_lines                               | no_whitespace_in_blank_line
-
-Changes to Fixers
------------------
-
-Fixer | Note
------ | ----
-psr0  | Fixer no longer takes base dir from `ConfigInterface::getDir`, instead you may configure the fixer with `['dir' => 'my/path']`.
-
-Custom fixers
--------------
-
-If you have registered custom fixers in your config file `*.php_cs` using `addCustomFixer()` method...
-```
-<?php
-// phpcs-fixer v1.*
-$config = Symfony\CS\Config\Config::create()
-    ->fixers([
-        'blankline_after_open_tag',
-        // ...
-    ])
-    ->addCustomFixer(new ShopSys\CodingStandards\CsFixer\MissingButtonTypeFixer())
-    ->addCustomFixer(new ShopSys\CodingStandards\CsFixer\OrmJoinColumnRequireNullableFixer());
-```
-...now you have to use `registerCustomFixers()` method instead and enable the custom fixers by their names in the `setRules()` method:
-```
-<?php
-// phpcs-fixer v2.*
-$config = PhpCsFixer\Config::create()
-    ->registerCustomFixers([
-        new ShopSys\CodingStandards\CsFixer\MissingButtonTypeFixer(),
-        new ShopSys\CodingStandards\CsFixer\OrmJoinColumnRequireNullableFixer(),
-    ])
-    ->setRules([
-        'blankline_after_open_tag',
-        'Shopsys/missing_button_type' => true,
-        'Shopsys/orm_join_column_require_nullable' => true,
-        // ...
-    ]);
-
-```

data/helpers/vendor/friendsofphp/php-cs-fixer/ci-integration.sh

@@ -1,8 +0,0 @@
-#!/bin/sh
-set -eu
-
-IFS='
-'
-CHANGED_FILES=$(git diff --name-only --diff-filter=ACMRTUXB "${COMMIT_RANGE}")
-if ! echo "${CHANGED_FILES}" | grep -qE "^(\\.php_cs(\\.dist)?|composer\\.lock)$"; then EXTRA_ARGS=$(printf -- '--path-mode=intersection\n--\n%s' "${CHANGED_FILES}"); else EXTRA_ARGS=''; fi
-vendor/bin/php-cs-fixer fix --config=.php_cs.dist -v --dry-run --stop-on-violation --using-cache=no ${EXTRA_ARGS}

data/helpers/vendor/friendsofphp/php-cs-fixer/composer.json

@@ -1,83 +0,0 @@
-{
-    "name": "friendsofphp/php-cs-fixer",
-    "type": "application",
-    "description": "A tool to automatically fix PHP code style",
-    "license": "MIT",
-    "authors": [
-        {
-            "name": "Fabien Potencier",
-            "email": "fabien@symfony.com"
-        },
-        {
-            "name": "Dariusz Rumiński",
-            "email": "dariusz.ruminski@gmail.com"
-        }
-    ],
-    "require": {
-        "php": "^5.6 || ^7.0",
-        "ext-json": "*",
-        "ext-tokenizer": "*",
-        "composer/semver": "^1.4",
-        "composer/xdebug-handler": "^1.2",
-        "doctrine/annotations": "^1.2",
-        "php-cs-fixer/diff": "^1.3",
-        "symfony/console": "^3.4.17 || ^4.1.6 || ^5.0",
-        "symfony/event-dispatcher": "^3.0 || ^4.0 || ^5.0",
-        "symfony/filesystem": "^3.0 || ^4.0 || ^5.0",
-        "symfony/finder": "^3.0 || ^4.0 || ^5.0",
-        "symfony/options-resolver": "^3.0 || ^4.0 || ^5.0",
-        "symfony/polyfill-php70": "^1.0",
-        "symfony/polyfill-php72": "^1.4",
-        "symfony/process": "^3.0 || ^4.0 || ^5.0",
-        "symfony/stopwatch": "^3.0 || ^4.0 || ^5.0"
-    },
-    "require-dev": {
-        "johnkary/phpunit-speedtrap": "^1.1 || ^2.0 || ^3.0",
-        "justinrainbow/json-schema": "^5.0",
-        "keradus/cli-executor": "^1.2",
-        "mikey179/vfsstream": "^1.6",
-        "php-coveralls/php-coveralls": "^2.1",
-        "php-cs-fixer/accessible-object": "^1.0",
-        "php-cs-fixer/phpunit-constraint-isidenticalstring": "^1.1",
-        "php-cs-fixer/phpunit-constraint-xmlmatchesxsd": "^1.1",
-        "phpunit/phpunit": "^5.7.27 || ^6.5.14 || ^7.1",
-        "phpunitgoodpractices/traits": "^1.8",
-        "symfony/phpunit-bridge": "^5.1",
-        "symfony/yaml": "^3.0 || ^4.0 || ^5.0"
-    },
-    "suggest": {
-        "ext-dom": "For handling output formats in XML",
-        "ext-mbstring": "For handling non-UTF8 characters.",
-        "php-cs-fixer/phpunit-constraint-isidenticalstring": "For IsIdenticalString constraint.",
-        "php-cs-fixer/phpunit-constraint-xmlmatchesxsd": "For XmlMatchesXsd constraint.",
-        "symfony/polyfill-mbstring": "When enabling `ext-mbstring` is not possible."
-    },
-    "config": {
-        "sort-packages": true
-    },
-    "autoload": {
-        "psr-4": {
-            "PhpCsFixer\\": "src/"
-        },
-        "classmap": [
-            "tests/Test/AbstractFixerTestCase.php",
-            "tests/Test/AbstractIntegrationCaseFactory.php",
-            "tests/Test/AbstractIntegrationTestCase.php",
-            "tests/Test/Assert/AssertTokensTrait.php",
-            "tests/Test/IntegrationCase.php",
-            "tests/Test/IntegrationCaseFactory.php",
-            "tests/Test/IntegrationCaseFactoryInterface.php",
-            "tests/Test/InternalIntegrationCaseFactory.php",
-            "tests/Test/IsIdenticalConstraint.php",
-            "tests/TestCase.php"
-        ]
-    },
-    "autoload-dev": {
-        "psr-4": {
-            "PhpCsFixer\\Tests\\": "tests/"
-        }
-    },
-    "bin": [
-        "php-cs-fixer"
-    ]
-}

data/helpers/vendor/friendsofphp/php-cs-fixer/doc/COOKBOOK-FIXERS.md

@@ -1,530 +0,0 @@
-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](https://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](https://en.wikipedia.org/wiki/Linus%27s_Law)).
-
-If possible, try to get acquainted with the public interface for the
-[Tokens class](/src/Tokenizer/Tokens.php)
-and [Token class](/src/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.
-* Installed the dependencies of PHP CS Fixer using [Composer](https://getcomposer.org/).
-* 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 `src/Fixer/Comment/RemoveCommentsFixer.php`.
-Put this content inside:
-```php
-<?php
-
-/*
- * This file is part of PHP CS Fixer.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *     Dariusz Rumiński <dariusz.ruminski@gmail.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
-
-namespace PhpCsFixer\Fixer\Comment;
-
-use PhpCsFixer\AbstractFixer;
-use PhpCsFixer\Tokenizer\Tokens;
-
-/**
- * @author Your name <your@email.com>
- */
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    /**
-     * {@inheritdoc}
-     */
-    public function getDefinition()
-    {
-        // Return a definition of the fixer, it will be used in the README.rst.
-    }
-
-    /**
-     * {@inheritdoc}
-     */
-    public function isCandidate(Tokens $tokens)
-    {
-        // Check whether the collection is a candidate for fixing.
-        // Has to be ultra cheap to execute.
-    }
-
-    /**
-     * {@inheritdoc}
-     */
-    protected function applyFix(\SplFileInfo $file, Tokens $tokens)
-    {
-        // Add the fixing logic of the fixer here.
-    }
-}
-```
-
-Note how the class and file name match. Also keep in mind that all
-fixers must implement `Fixer\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
-`tests/Fixer/Comment/RemoveCommentsFixerTest.php`. Put this content inside:
-
-```php
-<?php
-
-/*
- * This file is part of PHP CS Fixer.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *     Dariusz Rumiński <dariusz.ruminski@gmail.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
-
-namespace PhpCsFixer\Tests\Fixer\Comment;
-
-use PhpCsFixer\Tests\Test\AbstractFixerTestCase;
-
-/**
- * @author Your name <your@email.com>
- *
- * @internal
- *
- * @covers \PhpCsFixer\Fixer\Comment\RemoveCommentsFixer
- */
-final class RemoveCommentsFixerTest extends AbstractFixerTestCase
-{
-    /**
-     * @param string      $expected
-     * @param null|string $input
-     *
-     * @dataProvider provideFixCases
-     */
-    public function testFix($expected, $input = null)
-    {
-        $this->doTest($expected, $input);
-    }
-
-    public function provideFixCases()
-    {
-        return [];
-    }
-}
-```
-### 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:
-`tests/Fixer/Comment/RemoveCommentsFixerTest.php`@provideFixCases:
-```php
-    ...
-    public function provideFixCases()
-    {
-        return [
-            ['<?php echo "This should not be changed";'], // Each sub-array is a test
-        ];
-    }
-    ...
-```
-
-#### Ensuring things change:
-`tests/Fixer/Comment/RemoveCommentsFixerTest.php`@provideFixCases:
-```php
-    ...
-    public function provideFixCases()
-    {
-        return [
-            [
-                '<?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:
-`tests/Fixer/Comment/RemoveCommentsFixerTest.php`
-```php
-<?php
-
-/*
- * This file is part of PHP CS Fixer.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *     Dariusz Rumiński <dariusz.ruminski@gmail.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
-
-namespace PhpCsFixer\Tests\Fixer\Comment;
-
-use PhpCsFixer\Tests\Fixer\AbstractFixerTestBase;
-
-/**
- * @author Your name <your@email.com>
- *
- * @internal
- */
-final class RemoveCommentsFixerTest extends AbstractFixerTestBase
-{
-    /**
-     * @param string      $expected
-     * @param null|string $input
-     *
-     * @dataProvider provideFixCases
-     */
-    public function testFix($expected, $input = null)
-    {
-        $this->doTest($expected, $input);
-    }
-
-    public function provideFixCases()
-    {
-        return [
-            [
-               '<?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.
-
-First, we need to create one method to describe what this fixer does:
-`src/Fixer/Comment/RemoveCommentsFixer.php`:
-```php
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    /**
-     * {@inheritdoc}
-     */
-    public function getDefinition()
-    {
-        return new FixerDefinition(
-            'Removes all comments of the code that are preceded by ";" (semicolon).', // Trailing dot is important. We thrive to use English grammar properly.
-            [
-                new CodeSample(
-                    '<?php echo 123; /* Comment */'
-                ),
-            ]
-        );
-    }
-}
-```
-Next, we need to update the `README.rst`.
-Fortunately, PHP CS Fixer can help you here.
-Execute the following command in your command shell:
-
-`$ php php-cs-fixer readme > README.rst`
-
-Next, we must filter what type of tokens we want to fix. Here, we are interested in code that contains `T_COMMENT` tokens:
-`src/Fixer/Comment/RemoveCommentsFixer.php`:
-```php
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    ...
-
-    /**
-     * {@inheritdoc}
-     */
-    public function isCandidate(Tokens $tokens)
-    {
-        return $tokens->isTokenKindFound(T_COMMENT);
-    }
-}
-```
-
-For now, let us just make a fixer that applies no modification:
-`src/Fixer/Comment/RemoveCommentsFixer.php`:
-```php
-class RemoveCommentsFixer extends AbstractFixer
-{
-    ...
-
-    /**
-     * {@inheritdoc}
-     */
-    protected function applyFix(\SplFileInfo $file, Tokens $tokens)
-    {
-        // no action
-    }
-}
-```
-
-Run `$ phpunit tests/Fixer/Comment/RemoveCommentsFixerTest.php`.
-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"](https://php.net/manual/en/tokens.php).
-
-Internally, PHP CS Fixer transforms some of PHP native tokens into custom
-tokens through the use of [Transfomers](/src/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.
-`src/Fixer/Comment/RemoveCommentsFixer.php`:
-```php
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    ...
-
-    /**
-     * {@inheritdoc}
-     */
-    protected function applyFix(\SplFileInfo $file, Tokens $tokens)
-    {
-        foreach ($tokens as $index => $token) {
-            if (!$token->isGivenKind(T_COMMENT)) {
-                continue;
-            }
-
-            // need to figure out what to do here!
-        }
-    }
-}
-```
-
-OK, now for each `T_COMMENT`, all we need to do is check if the previous
-token is a semicolon.
-`src/Fixer/Comment/RemoveCommentsFixer.php`:
-```php
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    ...
-
-    /**
-     * {@inheritdoc}
-     */
-    protected function applyFix(\SplFileInfo $file, Tokens $tokens)
-    {
-        foreach ($tokens as $index => $token) {
-            if (!$token->isGivenKind(T_COMMENT)) {
-                continue;
-            }
-
-            $prevTokenIndex = $tokens->getPrevMeaningfulToken($index);
-            $prevToken = $tokens[$prevTokenIndex];
-
-            if ($prevToken->equals(';')) {
-                $tokens->clearAt($index);
-            }
-        }
-    }
-}
-```
-
-So the fixer in the end looks like this:
-```php
-<?php
-
-/*
- * This file is part of PHP CS Fixer.
- *
- * (c) Fabien Potencier <fabien@symfony.com>
- *     Dariusz Rumiński <dariusz.ruminski@gmail.com>
- *
- * This source file is subject to the MIT license that is bundled
- * with this source code in the file LICENSE.
- */
-
-namespace PhpCsFixer\Fixer\Comment;
-
-use PhpCsFixer\AbstractFixer;
-use PhpCsFixer\Tokenizer\Tokens;
-
-/**
- * @author Your name <your@email.com>
- */
-final class RemoveCommentsFixer extends AbstractFixer
-{
-    /**
-     * {@inheritdoc}
-     */
-    public function getDefinition()
-    {
-        return new FixerDefinition(
-            'Removes all comments of the code that are preceded by ";" (semicolon).', // Trailing dot is important. We thrive to use English grammar properly.
-            [
-                new CodeSample(
-                    '<?php echo 123; /* Comment */'
-                ),
-            ]
-        );
-    }
-
-    /**
-     * {@inheritdoc}
-     */
-    public function isCandidate(Tokens $tokens)
-    {
-        return $tokens->isTokenKindFound(T_COMMENT);
-    }
-
-    /**
-     * {@inheritdoc}
-     */
-    protected function applyFix(\SplFileInfo $file, Tokens $tokens) {
-        foreach($tokens as $index => $token){
-            if (!$token->isGivenKind(T_COMMENT)) {
-                continue;
-            }
-
-            $prevTokenIndex = $tokens->getPrevMeaningfulToken($index);
-            $prevToken = $tokens[$prevTokenIndex];
-
-            if ($prevToken->equals(';')) {
-                $tokens->clearAt($index);
-            }
-        }
-    }
-}
-```
-
-### 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 add it to existing ruleset.
-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.
-
-#### 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 `->`.