Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Now that #2870645: PHPCS is failing on contrib modules is fixed, D8 contrib module automated testing is running code sniffs to check for coding standards violations in this module.
The latest test reported two minor errors:
FILE: .../modules/contrib/config_update/src/ConfigListerWithProviders.php
----------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------
10 | WARNING | [x] Unused use statement
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------
FILE: ...pdate/config_update_ui/src/Controller/ConfigUpdateController.php
----------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 2 LINES
----------------------------------------------------------------------
71 | ERROR | [ ] Parameter $config_factory is not described in
| | comment
86 | ERROR | [x] Separate the @param and @praam sections by a blank
| | line.
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------
This should be trivial to patch... I think for the second one, the problem is an @param with a typo that says @praam instead, and the first one just needs to have a use statement removed.
Comment | File | Size | Author |
---|---|---|---|
#4 | coding-standard-errors-2901018-4.patch | 1.46 KB | arunkumark |
| |||
#2 | coding-standard-errors-2901018-2.patch | 1.1 KB | arunkumark |
|
Comments
Comment #2
arunkumarkGood catch @jhodgdon
I have patched for fixing the Coding standards.
Comment #3
jhodgdonThanks for the patch! However, it only fixed the first error.
For the second error, as I said in the issue summary:
"the problem is an @param with a typo that says @praam instead"
So that needs a different patch.
Comment #4
arunkumark@jhodgdon thanks for the comment. I have rerolled the patch by fixing all Coding standards issues.
Comment #5
arunkumarkComment #7
jhodgdonThanks -- yes, that is the correct patch. Committed.