Problem/Motivation

Postponed on #2857906: Enforce short array syntax for Drupal 8 api docblock comments

This is a follow-up to #2868078: Use new array syntax in PHP files outside of /core..

The coding standards for arrays require short array syntax (except for Drupal 7 core and contributed modules). Does this apply to code samples inside @code blocks? If so, then we need to

  1. Clarify this requirement in the documentation.
  2. Check array syntax inside @code blocks in our CodeSniffer sniffs.
  3. Update Drupal core to use the short syntax inside @code blocks.

Steps to reproduce

Proposed resolution

Add the new sniff, <rule ref="Drupal.Commenting.DocCommentLongArraySyntax"/> to phpcs.xml.dist
Run phpcs on core
Fix the errors found

Remaining tasks

See #46 Followup for use @code/@endcode where possible #3454142: Convert long array syntax in comments
See #47 Followup to fix array() in sentences. #3454159: Convert use of array() syntax in sentences
Patch
Review
Commit

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Release notes snippet

Issue fork drupal-2874067

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

Status: Active » Needs review
StatusFileSize
new19.05 KB

The attached patch is a start. It is the same as the interdiff from #2868078-22: Use new array syntax in PHP files outside of /core.. It only changes array syntax inside @code blocks in files outside the core/ directory.

Status: Needs review » Needs work

The last submitted patch, 2: 2874067-2.patch, failed testing.

benjifisher’s picture

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

benjifisher’s picture

Oops, I think I got the patch reversed.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

MerryHamster’s picture

StatusFileSize
new133.46 KB

here my variant the patch for 8.6.x
when I have been beginning I did not think that I will have found so many places where need to do changes

MerryHamster’s picture

Status: Needs work » Needs review
sk33lz’s picture

Patch #8 applies cleanly to 8.6.x with no offsets. I don't know if this updates all code samples throughout core, but all the ones I reviewed that it updated look great so far.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Title: Use short array syntax inside @code blocks » Fix short array syntax in doc blocks
Version: 9.3.x-dev » 9.4.x-dev
Issue summary: View changes
Status: Needs review » Postponed
Issue tags: +Coding standards
Parent issue: » #2571965: [meta] Fix PHP coding standards in core, stage 1
dww’s picture

I foolishly opened #3273865: Correct use of array() to [] in comments (to remove a 'Needs followup' tag at #3265929: Rewrite examples of form options to be less culturally specific) without first searching. @quietone helpfully pointed me here.

However, the coder sniff linked here only handles stuff inside @code blocks. My initial manual effort at #3273865 found some spots where array() was used in comments that were missing @code blocks. I started added the @code/@endcode. But now it's a bit of a tangled mess. Perhaps we should re-purpose/re-open #3273865 to specifically handle all the edge cases where we're missing @code blocks?

quietone’s picture

Yes, that sounds good to me. And I will make a patch from the MR over there and post it here so that any fixes you made can be merged into this one at a later date.

quietone’s picture

StatusFileSize
new47.44 KB

Uploaded the patch from duplicate issue here as it contains files not changed in the existing patch. Adding credit for dww.

dww’s picture

Status: Postponed » Needs work

The coder issue is now fixed. Guess we need to regenerate a patch in here now to use that, so back to NW.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

kunalgautam’s picture

Status: Needs work » Needs review
StatusFileSize
new3.29 KB

Here patch for 10.1.x

jay jangid’s picture

Assigned: Unassigned » jay jangid
jay jangid’s picture

Assigned: jay jangid » Unassigned

I have applied the patch #24 in Drupal 10.1.x version and it is working fine.
Thanks for the patch.
Results :-Fix short array syntax in "core.api.php".

smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative

Comparing #24 with #8 seems to be missing a big chunk of the fixes.

Some of them may have naturally been fixed but the few files I checked they have not.

kunalgautam’s picture

StatusFileSize
new122.54 KB

Thanks @smustgrave this is the updated patch

kunalgautam’s picture

Status: Needs work » Needs review
smustgrave’s picture

Status: Needs review » Needs work

CI failure #28

kunalgautam’s picture

StatusFileSize
new121.6 KB

Updated the patch

kunalgautam’s picture

StatusFileSize
new122.41 KB
quietone’s picture

Title: Fix short array syntax in doc blocks » Fix Drupal.Commenting.DocCommentLongArraySyntax coding standard
Issue summary: View changes

Nice to see progress here!

Fixing PHP coding standards is done by first adding a Coder rule, or sniff. The current patch is missing that so it needs to be added.We do this so that new code does not introduce regressions. When a patch is tested various checks are run, such as coding standard checks, before the tests run.

So, what needs to happen here is to start by just adding the sniff. Then run phpcs to find what needs to be fixed. Then fix the comments and run phpcs core until there are no errors. The latest patch will have some of those fixes but it also contains out of scope changes. This patch is to fix array syntax in comments, not code.

I have updated the proposed resolution in the Issue Summary with some details.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nlisgo made their first commit to this issue’s fork.

nikolay shapovalov’s picture

Assigned: Unassigned » nikolay shapovalov
nikolay shapovalov’s picture

Assigned: nikolay shapovalov » Unassigned
Status: Needs work » Needs review
StatusFileSize
new123.12 KB
new18.37 KB

I update phpcs.xml and remove unwanted changes.
I was not able to apply patch 32, so I made some changes to it, I added manually created interdiff.
Please review.

nikolay shapovalov’s picture

StatusFileSize
new123.12 KB
new18.37 KB

Oops, made mistake when creating a patch file.
Provide new patch file and interdiff.

nikolay shapovalov’s picture

StatusFileSize
new18.37 KB

Update interdiff #32 and #38.

needs-review-queue-bot’s picture

Status: Needs review » Needs work

The Needs Review Queue Bot tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request. Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

nikolay shapovalov’s picture

Status: Needs work » Needs review

I created MR as requested by Needs Review Queue Bot.

nikolay shapovalov’s picture

Hide patch files.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Failure is random and unrelated, ran it a few times and sometimes it passes sometimes fails but is not impacted by this
#3317520: [random test failure] Drupal\Tests\settings_tray\FunctionalJavascript\SettingsTrayBlockFormTest::testEditModeEnableDisable

Large MR but not terrible to read.

Think if anything was missed the phpcs line added would of got it.

xjm’s picture

As the person who reviewed and committed the 12-gigabyte array() to [] conversion, I feel it's my very great honor to review this one as well.

xjm’s picture

Issue tags: +Needs followup

Something odd is going on with the docblock of EntityFormDisplayInterface::buildForm(); there are more array openings than closures. It appears to be pseudocode rather than example code, and at least one array closure was missed. That's an existing problem and out of scope for a color-words issue like this, so tagging for a followup.

xjm’s picture

Status: Reviewed & tested by the community » Needs review

I reviewed this locally with git diff --color-words to verify that all the changes were complete and correct replacements of array() with [] in API documentation.

There was another existing issue in core/modules/views/src/Plugin/views/cache/CachePluginBase.php with a missing closing paren that's fixed here. I opened the file locally to confirm that it's fixed correctly.

I also grepped the codebase to check for remaining array(). There are many in inline comments, but that seems to be outside the scope of this issue, which is all docblocks. So, I think we need a second followup for inline comments.

However, there are somehow also numerous instances in docblocks that are apparently not being caught by the rule?

[ayrton:maintainer | Thu 18:37:29] $ grep -r "\barray(" * | grep -F \* | grep -v "vendor" | grep -v "node_modules"
core/scripts/dump-database-d7.sh:  $result = db_query('SELECT * FROM {'. $table .'}', array(), array('fetch' => PDO::FETCH_ASSOC));
core/lib/Drupal/Core/Database/Database.php:   * array(
core/lib/Drupal/Core/Database/Log.php:   * array(
core/lib/Drupal/Core/Database/Log.php:   *   $logging_key = array(
core/lib/Drupal/Core/Database/Log.php:   *     array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0, 'start' => 0),
core/lib/Drupal/Core/Database/Log.php:   *     array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0, 'start' => 0),
core/lib/Drupal/Core/Database/Query/Select.php:   * array(
core/lib/Drupal/Core/Cache/UseCacheBackendTrait.php:   *   tags. For example array('node' => array(123), 'user' => array(92)).
core/lib/Drupal/Core/Datetime/DrupalDateTime.php: * DrupalDateTime::createFromArray( array('year' => 2010, 'month' => 9, 'day' => 28) )
core/lib/Drupal/Core/Entity/EntityAutocompleteMatcherInterface.php:   *   autocomplete API (e.g. array('value' => $value, 'label' => $label)).
core/lib/Drupal/Core/Render/Element.php:   *   property; e.g., array('#property_name' => 'attribute_name'). If both
core/lib/Drupal/Core/ImageToolkit/ImageToolkitInterface.php:   *   operation, e.g. array('width' => 50, 'height' => 100,
core/lib/Drupal/Core/Field/FieldConfigInterface.php:   *   - NULL or array() for no default value.
core/lib/Drupal/Core/Field/FieldDefinitionInterface.php:   *   each item being a property/value array (array() for no default value).
core/lib/Drupal/Core/Field/FieldDefinitionInterface.php:   *   each item being a property/value array (array() for no default value).
core/lib/Drupal/Core/Field/BaseFieldDefinition.php:   *   each item being a property/value array (array() for no default value).
core/lib/Drupal/Core/Utility/ProjectInfo.php:   *   file. Defaults to array().
core/lib/Drupal/Core/Utility/ProjectInfo.php:   *   file. Defaults to array().
core/lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
core/lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
core/lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
core/modules/views_ui/admin.inc: *   array('dynamic_content', 'section') for this parameter.
core/modules/system/tests/modules/common_test/common_test.module: * \Drupal::moduleHandler()->alter(array(TYPE1, TYPE2), ...) allows
core/modules/page_cache/src/StackMiddleware/PageCache.php:   *   tags. For example array('node' => array(123), 'user' => array(92)).
core/modules/views/src/Plugin/views/wizard/WizardPluginBase.php:   *   normally be found in $form_state->getValue(array('wrapper', 'select')),
core/modules/views/src/Plugin/views/wizard/WizardPluginBase.php:   *   you would pass array('wrapper', 'select') for this parameter.
core/modules/views/src/Plugin/views/field/Markup.php: *           array('field' => {$field}) where $field is the field in this table
core/modules/rest/src/Plugin/ResourceInterface.php:   *   The list of supported methods. Example: array('GET', 'POST', 'PATCH').

Setting NR to look into those. Several of them appear to be in sentences rather than @code/@endcode -- maybe that is the common factor? If that's confirmed, we could have a third followup to properly use @code where possible and a fourth to fix them in sentences.

Thanks everyone!

smustgrave’s picture

Then how come the rule didn’t catch those?

quietone’s picture

Issue summary: View changes

@smustgrave, yes that is the question that xjm is asking those working on this issue to answer.

To help move this along I did the following. I started by searching the vendor directory for DocCommentLongArraySyntax and found the class implementing the sniff.

/**
 * Ensures @code annotations in doc blocks don't contain long array syntax.
 *
 * @category PHP
 * @package  PHP_CodeSniffer
 * @link     http://pear.php.net/package/PHP_CodeSniffer
 */
class DocCommentLongArraySyntaxSniff implements Sniff
{

The summary line confirms what xjm suspected in #47. And as I read it then the remainder of the work in #47 can proceed.

I have added #46 and #47 to the remaining tasks.

smustgrave’s picture

Status: Needs review » Needs work

For the follow ups of 46 + 47

quietone’s picture

Issue summary: View changes
Status: Needs work » Needs review

Rebased the MR. Then, I searched for the same pattern used in #47 and then checked the files and I am confident these are not detected because they are not in @code @endcode blocks. I have updated the issue summary with the followups that need to be made.

smustgrave’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

So applied the MR and ran grep -r "\barray(" * | grep -F \* | grep -v "vendor" | grep -v "node_modules"

lib/Drupal/Core/Database/Database.php:   * array(
lib/Drupal/Core/Database/Log.php:   * array(
lib/Drupal/Core/Database/Log.php:   *   $logging_key = array(
lib/Drupal/Core/Database/Log.php:   *     array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0, 'start' => 0),
lib/Drupal/Core/Database/Log.php:   *     array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0, 'start' => 0),
lib/Drupal/Core/Database/Query/Select.php:   * array(
lib/Drupal/Core/Cache/UseCacheBackendTrait.php:   *   tags. For example array('node' => array(123), 'user' => array(92)).
lib/Drupal/Core/Datetime/DrupalDateTime.php: * DrupalDateTime::createFromArray( array('year' => 2010, 'month' => 9, 'day' => 28) )
lib/Drupal/Core/Entity/EntityAutocompleteMatcherInterface.php:   *   autocomplete API (e.g. array('value' => $value, 'label' => $label)).
lib/Drupal/Core/Render/Element.php:   *   property; e.g., array('#property_name' => 'attribute_name'). If both
lib/Drupal/Core/ImageToolkit/ImageToolkitInterface.php:   *   operation, e.g. array('width' => 50, 'height' => 100,
lib/Drupal/Core/Field/FieldConfigInterface.php:   *   - NULL or array() for no default value.
lib/Drupal/Core/Field/FieldDefinitionInterface.php:   *   each item being a property/value array (array() for no default value).
lib/Drupal/Core/Field/FieldDefinitionInterface.php:   *   each item being a property/value array (array() for no default value).
lib/Drupal/Core/Field/BaseFieldDefinition.php:   *   each item being a property/value array (array() for no default value).
lib/Drupal/Core/Utility/ProjectInfo.php:   *   file. Defaults to array().
lib/Drupal/Core/Utility/ProjectInfo.php:   *   file. Defaults to array().
lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
lib/Drupal/Component/Gettext/PoHeader.php:   *   array(
modules/views_ui/admin.inc: *   array('dynamic_content', 'section') for this parameter.
modules/system/tests/modules/common_test/common_test.module: * \Drupal::moduleHandler()->alter(array(TYPE1, TYPE2), ...) allows
modules/page_cache/src/StackMiddleware/PageCache.php:   *   tags. For example array('node' => array(123), 'user' => array(92)).
modules/views/src/Plugin/views/wizard/WizardPluginBase.php:   *   normally be found in $form_state->getValue(array('wrapper', 'select')),
modules/views/src/Plugin/views/wizard/WizardPluginBase.php:   *   you would pass array('wrapper', 'select') for this parameter.
modules/views/src/Plugin/views/field/Markup.php: *           array('field' => {$field}) where $field is the field in this table
modules/rest/src/Plugin/ResourceInterface.php:   *   The list of supported methods. Example: array('GET', 'POST', 'PATCH').
scripts/dump-database-d7.sh:  $result = db_query('SELECT * FROM {'. $table .'}', array(), array('fetch' => PDO::FETCH_ASSOC));

Which spot checking appear to be outside of @code blocks.

For #45 follow up is that covered by #3454142: Convert long array syntax in comments or #3454159: Convert use of array() syntax in sentences ?

xjm’s picture

Status: Reviewed & tested by the community » Needs work

There is a hunk in core/modules/views/src/Plugin/views/field/FieldPluginBase.php that has out-of-scope changes. It could either be a bad merge, or someone correcting the documentation while fixing this bug.

If it's the latter, we should make a followup issue to correct the keys; regardless, the hunk should only include the changes to array().

Going to do a local review of this with git diff --color-words; if someone wants to fix the hunk and file a followup if appropriate, we could get this in still as a beta phase(-ish) cleanup.

Saving issue credits.

xjm’s picture

Issue tags: -Needs followup +Novice

Followups were already created.

Tagging "Novice" for the task described in #53.

smustgrave’s picture

Status: Needs work » Reviewed & tested by the community
Related issues: +#3455127: Update use of arguments used in comments

#3455127: Update use of arguments used in comments opened, already tagged for title update cuz that one is bad.

smustgrave’s picture

Oops did that before I got the novice email.

xjm’s picture

Issue tags: -Novice

No worries, I prefer to just land the issue in this case. :D

  • xjm committed bd12c418 on 11.x
    Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, smustgrave...

  • xjm committed 8fedc4e2 on 11.0.x
    Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, smustgrave...
xjm’s picture

Version: 11.x-dev » 10.4.x-dev

Committed to 11.x and 11.0.x.

It cherry-picked cleanly to 10.4.x with some auto-merging, but I'm going to open a quick 10.4.x MR here based on that cherry-pick just to ensure there aren't additional instances in D10 that would cause the rule to fail there.

xjm’s picture

Status: Reviewed & tested by the community » Needs work

Good thing I tested that backport before pushing it; looks like the 10.4.x backport will need some additions. :D

--------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------
 258 | ERROR | Long array syntax must not be used in doc comment code
     |       | annotations
     |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
--------------------------------------------------------------------------------
FILE: ...ds/project/drupal/core/modules/tour/tests/src/Functional/TourTestBasic.php
--------------------------------------------------------------------------------
FOUND 4 ERRORS AFFECTING 4 LINES
--------------------------------------------------------------------------------
 19 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 20 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 21 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 22 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
--------------------------------------------------------------------------------
FILE: ...lds/project/drupal/core/modules/tour/tests/src/Functional/TourTestBase.php
--------------------------------------------------------------------------------
FOUND 4 ERRORS AFFECTING 4 LINES
--------------------------------------------------------------------------------
 23 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 24 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 25 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
 26 | ERROR | Long array syntax must not be used in doc comment code
    |       | annotations
    |       | (Drupal.Commenting.DocCommentLongArraySyntax.DocLongArray)
--------------------------------------------------------------------------------
Time: 10.49 secs; Memory: 8MB
PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------
FILE                                                            ERRORS  WARNINGS
--------------------------------------------------------------------------------
/builds/project/drupal/core/includes/install.inc                1       0
...pal/core/modules/tour/tests/src/Functional/TourTestBase.php  4       0
...al/core/modules/tour/tests/src/Functional/TourTestBasic.php  4       0
--------------------------------------------------------------------------------
A TOTAL OF 9 ERRORS AND 0 WARNINGS WERE FOUND IN 3 FILES
--------------------------------------------------------------------------------

b_sharpe made their first commit to this issue’s fork.

b_sharpe’s picture

Status: Needs work » Needs review

Fixed up 10.4 backport, passing phpcs now.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

10.4 rebase seems fine.

xjm’s picture

Thanks @b_sharpe, nice work!

  • xjm committed fcfcbc6d on 10.4.x
    Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, b_sharpe,...
xjm’s picture

Version: 10.4.x-dev » 10.3.x-dev
Status: Reviewed & tested by the community » Fixed

Since 10.3.x is in RC, it is not eligible to have new rules enabled. So, instead of testing a 10.3.x backport, I backported the 10.4.x changes only for parity, then removed the rule addition, with the following commands:

[ayrton:maintainer | Mon 15:24:12] $ git cherry-pick -x 10.4.x
Auto-merging core/modules/responsive_image/responsive_image.module
[10.3.x e64d867c62] Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, b_sharpe, smustgrave, xjm, benjifisher, MerryHamster, dww: Fix Drupal.Commenting.DocCommentLongArraySyntax coding standard
 Date: Mon Jun 17 15:22:41 2024 -0500
 107 files changed, 579 insertions(+), 578 deletions(-)

[ayrton:maintainer | Mon 15:24:20] $ git checkout HEAD^ --  core/phpcs.xml.dist  

[ayrton:maintainer | Mon 15:27:29] $ git commit --amend -m 'Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, b_sharpe, smustgrave, xjm, benjifisher, MerryHamster, dww: Fix Drupal.Commenting.DocCommentLongArraySyntax coding standard'

Thanks everyone!

  • xjm committed 23f09d3f on 10.3.x
    Issue #2874067 by kkalashnikov, Nikolay Shapovalov, quietone, b_sharpe,...

Status: Fixed » Closed (fixed)

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