Part of #2571965: [meta] Fix PHP coding standards in core.

Approach

We are testing coding standards with PHP CodeSniffer, using the Drupal coding standards from the Coder module. Both of these packages are not installed in Drupal core. We need to do a couple of steps in order to download and configure them so we can run a coding standards check.

Step 1: Add the coding standard to the whitelist

Every coding standard is identified by a "sniff". For example, an imaginary coding standard that would require all llamas to be placed inside a square bracket fence would be called the "Drupal.AnimalControlStructure.BracketedFence sniff". There are dozens of such coding standards, and to make the work easier we have started by only whitelisting the sniffs that pass. For the moment all coding standards that are not yet fixed are simply skipped during the test.

Open the file core/phpcs.xml.dist and add a line for the sniff of this ticket. The sniff name is in the issue title. Make sure your patch will include the addition of this line.

Step 2: Install PHP CodeSniffer and the ruleset from the Coder module

Both of these packages are not installed by default in Drupal core, so we need to download them. This can be done with Composer, from the root folder of your Drupal installation:

$ composer require drupal/coder squizlabs/php_codesniffer
$ ./vendor/bin/phpcs --config-set installed_paths ../../drupal/coder/coder_sniffer

Once you have installed the phpcs package, you can list all the sniffs available to you like this:

$ ./vendor/bin/phpcs --standard=Drupal -e

This will give you a big list of sniffs, and the Drupal-based ones should be present.

Step 3: Prepare the phpcs.xml file

To speed up the testing you should make a copy of the file phpcs.xml.dist (in the core/ folder) and save it as phpcs.xml. This is the configuration file for PHP CodeSniffer.

We only want this phpcs.xml file to specify the sniff we're interested in. So we need to remove all the rule items, and add only our own sniff's rule. Rule items look like this:

<rule ref="Drupal.Classes.UnusedUseStatement"/>

Remove all of them, and add only the sniff from this issue title. This will make sure that our tests run quickly, and are not going to contain any output from unrelated sniffs.

Step 4: Run the test

Now you are ready to run the test! From within the core/ folder, run the following command to launch the test:

$ cd core/
$ ../vendor/bin/phpcs -p

This takes a couple of minutes. The -p flag shows the progress, so you have a bunch of nice dots to look at while it is running.

Step 5: Fix the failures

When the test is complete it will present you a list of all the files that contain violations of your sniff, and the line numbers where the violations occur. You could fix all of these manually, but thankfully phpcbf can fix many of them. You can call phpcbf like this:

$ ../vendor/bin/phpcbf

This will fix the errors in place. You can then make a diff of the changes using git. You can also re-run the test with phpcs and determine if that fixed all of them.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mfernea created an issue. See original summary.

mfernea’s picture

Status: Active » Postponed
mfernea’s picture

Status: Postponed » Needs review
FileSize
1.86 KB

Actually this does not depend on #2715485: Fix 'Drupal.Commenting.InlineComment.NoSpaceBefore' coding standard. Here is the patch.

xjm’s picture

I posted #2909373: Views TaxonomyIndexTidDepth has a weird commented IN condition to figure out what to do with this comment, but we can fix the standard on it and enable the rules.

xjm’s picture

Malevi4’s picture

I checked patch drupal-coding-standards-2909163-3.patch by mfernea and discover that all fine.

mfernea’s picture

Actually, we only have to include the sniff which is now passing.

mfernea’s picture

borisson_’s picture

Status: Needs review » Reviewed & tested by the community

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 8: drupal-coding-standards-2909163-6.patch, failed testing. View results

mfernea’s picture

Status: Needs work » Needs review
FileSize
1.03 KB

Re-roll.

borisson_’s picture

Status: Needs review » Reviewed & tested by the community

Back to rtbc

  • xjm committed af3691e on 8.5.x
    Issue #2909163 by mfernea: Fix 'Drupal.Commenting.InlineComment....

  • xjm committed a49a002 on 8.4.x
    Issue #2909163 by mfernea: Fix 'Drupal.Commenting.InlineComment....
xjm’s picture

Status: Reviewed & tested by the community » Fixed

I confirmed this rule does indeed pass now on 8.5.x. Also ran the phpcs suite against 8.4.x to make sure there weren't any differences between the two branches that would make it fail.

Committed to 8.5.x and cherry-picked to 8.4.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.