The Needs Review Queue Bot โ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide โ to find step-by-step guides for working with issues.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 8:56am 3 February 2023 - ๐ฎ๐ณIndia nayana_mvr
Reviewed the patch #46 and tested it on Drupal version 10.1.x. The patch applied cleanly and the spacing issues mentioned in the ticket are fixed. I can see that some coding standard issue are also fixed along with this patch but now there are some other coding standard issues. Please see the attached files for reference.
- Status changed to Needs work
almost 2 years ago 5:06pm 18 February 2023 - ๐บ๐ธUnited States smustgrave
Should instances like
/**
* @SomeAnnotationClassNameWithoutConstructor(data = "Some data")
*/
DOCBLOCK;Also be adjusted?
How come this wasn't caught by phpstan rules?
Kaushik1216 โ made their first commit to this issueโs fork.
- @kaushik1216 opened merge request.
- First commit to issue fork.
- First commit to issue fork.
- Status changed to Needs review
almost 2 years ago 5:08am 14 March 2023 - Status changed to Closed: won't fix
almost 2 years ago 5:52am 14 March 2023 - ๐ณ๐ฟNew Zealand quietone
Thanks for the interest in working on Drupal coding standards โ !
Unfortunately, what has been missed here is that ./core/tests/Drupal/Tests/Component/Annotation/Doctrine/ is specifically excluded from Coding standards. In phpcs.xml.dist there is this block:
<!-- Exclude third-party code maintained within core that does not follow our standards. --> <!-- @todo This rule may be removed when https://www.drupal.org/node/1848264 is resolved. --> <exclude-pattern>./core/lib/Drupal/Component/Diff/</exclude-pattern> <exclude-pattern>./core/tests/Drupal/Tests/Component/Annotation/Doctrine/</exclude-pattern>
were we see the comment tells use that this is "third-party code" and it does not meet our standards.
Another thing to know is that in order to fix core coding standards in a maintainable way, all our coding standards issues should be done on a per-rule basis across all of core, rather than fixing standards in individual modules or files. The meta issue for coding standards is ๐ [Meta] Fix coding standards in core Active . From there you can find the child issues for PHP, which is a Meta listing many child issues. If you wish to continue working to get Drupal to comply with our Coding Standards, I suggest selecting one of the existing child issues that needs work to complete.
There is also a Drupal Slack channel, #coding-standards, where you can join others interested in the Coding Standards process in Drupal core.
Cheers!