Problem/Motivation
This sniff relates to Drupal API documentation standards for classes and namespaces.
Hello this fixes the Drupal.Commenting.ClassComment.Missing standard listed in this parent, #2571965: [meta] Fix PHP coding standards in core, stage 1.
In the pull request two classes are skipped:
- one is being fixed via the https://www.drupal.org/project/drupal/issues/3105880
- and another one intentionally doesn't include the class doc block due to testing the empty plugin annotations (therefore the adjusted phpcs.xml.dist).
Steps to reproduce
Proposed resolution
Comply with Drupal API documentation standards for classes and namespaces and another relevant part of the Drupal coding standards.
Remaining tasks
This issue will enable the sniff and fix any remaining issues. The remaining issues will, at least, include core/lib.
Done
- module #3498302: Fix 'Drupal.Commenting.ClassComment.Missing' in modules
- Core test #3498158: Fix 'Drupal.Commenting.ClassComment.Missing' in core/tests
- Functional tests #3498152: Fix 'Drupal.Commenting.ClassComment.Missing' in Functional tests
- test modules #3498297: Fix 'Drupal.Commenting.ClassComment.Missing' in test modules
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|
Issue fork drupal-3105950
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
Comment #2
peterkokot commentedComment #3
peterkokot commentedComment #4
peterkokot commentedComment #8
spokjeComment #10
spokjeComment #11
quietone commentedI have done a very brief review, only looking at migrate files and then RDF and Rest. I am struck by the fact that a well formed name doesn't really need a doc bloc, but it is what it is. From my brief look I wonder about when to use English words instead of the class name. For example, this
* Interface for the migration executable.changes MigrateExecutable to migration executable but this* ResourceTestBase for RestResourceConfig entity.makes no such change.What is the approach to this?
Comment #13
spokje@quietone in #11.
My approach was too random indeed, trying to use full English words this time.
Comment #14
spokjeOk, I tried to use as much decent English as possible.
Beware: I'm not a native speaker, so I might have missed/messed up a few/lot.
I learned it from a book...
Comment #15
spokjeComment #16
quietone commentedUpdate IS.
Comment #17
quietone commentedComment #18
spokjeComment #19
spokjeThanks @quietone!
- Resolved all but one thread.
- Merged latest
9.3.xinto MR.- Found and fixed some new offenders.
Comment #20
spokje#WhyDoIAlwaysForgetToDoThisInThePreviousPost
Comment #21
spokjeComment #22
spokjeNot quite sure what happened here, but all is well now.
Comment #23
quietone commented@Spokje, thanks.
I think that is all I can do here. I do think this needs another set of eyes before RTBC.
Comment #24
spokjeThanks (Yet Again) @quietone.
Back to
Needs ReviewforComment #25
daffie commentedComment #26
spokjeResolved 2 old threads and added a comment on the new one by @daffie (thanks for the review)
Comment #27
spokje- Rebased MR on
9.4.x- Merged latest commits on
9.4.x- Fixed new offenders
- Resolved last open thread (thanks @daffie)
Comment #28
longwaveNice work - adding all these is quite tedious but it's good to finally get this one done.
Reviewed the full set of changes, added some suggestions where there are typos or I think we could improve wording, left a few other comments on places that didn't make sense to me when I read the sentence on its own.
Comment #29
spokjeThanks @longwave for Yet Another Review!
Resolved (hopefully successful) all threads.
Comment #30
spokjeMR is now against
9.4.x-devComment #31
longwaveThanks! I've re-read the whole MR and have no further suggestions. I'm sure there's more nitpicking that can be done (and our existing class comments also probably need work in places), but quietone, daffie and I have all had a go at reviewing this so I think it's had plenty of eyes on it now and is ready for commit.
Comment #32
alexpottWe're going to need a version of this that applies to 10.0.x - sorry. Plus it needs to be rerolled against 9.4.x
Comment #34
ankithashettyRebased the MR against 9.4.x branch, thanks!
Comment #38
ankithashettyHere is an MR for 10.0.x branch.
Changes made to
files in 9.4.x MR is ignored in this new MR as they no longer exist in 10.0.x branch.
Thanks!
Comment #39
quietone commentedAdd parent issue
Comment #42
smustgrave commentedMR needs to be updated for 10.1.x now.
If someone could chim in what else is needed for it to make it this round.
Comment #44
quietone commentedComment #45
quietone commentedComment #46
quietone commentedComment #47
quietone commentedComment #48
quietone commentedComment #49
quietone commentedRebased MR1889 onto 11.x and updated phpcs.xml.dist. This will need another rebase when the child issues are fixed.
Comment #50
quietone commentedComment #51
quietone commentedComment #52
quietone commentedTime for review.
Comment #53
borisson_These changes look good. It also has the change to phpcs.xml.dist to prevent regressions.
Comment #56
nod_Committed 96df9dd and pushed to 11.x. Thanks!