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.
I can see there has been an improvement in coder-module.
- https://www.drupal.org/project/coder/releases/8.x-3.5
- https://www.drupal.org/project/coder/releases/8.x-3.6
We need this to un-postpone #2937513: Fix 'Drupal.Commenting.DocComment.TagGroupSpacing' coding standard.
Comment | File | Size | Author |
---|---|---|---|
#9 | 3063323-9.patch | 7.35 KB | idebr |
Comments
Comment #2
truls1502Adding patch for
composer.lock
file.Comment #3
truls1502Comment #4
klausiThis needs to be created against 8.8.x. I just released Coder 8.3.6, so we should update to that.
Comment #5
klausiPatch, includes some minor fixes that Coder would flag now.
I hd to move around some @code sections because Coder would think they belong to the @param comment. However, general example docs about a function should be above param docs anyway.
Comment #6
idebr CreditAttribution: idebr at ezCompany commentedRunning `composer phpcs` locally with drupal/coder 8.3.6 results in a large number of reports regarding the
\Drupal\Sniffs\Commenting\VariableCommentSniff
:Was this sniff updated between 8.3.4 and 8.3.6? If so, should its fix be included in this issue?
Comment #7
klausiYes, VariableCommentSniff was updated in #2909393: Find missing comments for member variables. This sniff is disabled in core in phpcs.xml.dist, so does not affect this update.
Can you run the following and verify that the output of PHPCS is empty? (Adjust installed_paths to your local path)
Thanks!
Comment #8
idebr CreditAttribution: idebr at ezCompany commentedClosed #3074773: Updating drupal/coder (8.3.4 => 8.3.6): composer.lock as a duplicate issue.
Comment #9
idebr CreditAttribution: idebr at ezCompany commented#7 Actually
Drupal.Commenting.VariableComment
is enabled in core/phpcs.xml.dist. That means the new 'Missing' that was added in #2909393: Find missing comments for member variables has to be disabled for the existing code to pass. I have updated core/phpcs.xml.dist accordingly.Comment #10
klausiAh, good point, thank you!
I did not know about running "composer phpcs", that is useful! Output from that does not report errors with this patch after running composer install, so we should be good here.
I had to run it as "COMPOSER_PROCESS_TIMEOUT=10000 composer phpcs -- -p" to work around the composer timeout, we should disable that for phpcs with https://getcomposer.org/doc/06-config.md#process-timeout in a separate issue.
Comment #11
larowlanis this change required?
Comment #12
klausiYes, there was a fix in coder that flags this now.
Comment #13
larowlanCommitted 0192048 and pushed to 8.8.x. Thanks!
Comment #16
xjm