The include files in D8 core/includes are inconsistent with how they start. Sometimes @use statements are before the @file docblock and other times afterwards. There even is one case of @file directive missing altogether. In addition, some of the blocks of @use directives are in seemingly random order while other are in alphabetical order.
This issue is to clean up these files for the above.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1805594-1-include-headers.patch | 7.68 KB | lars toomre |
Comments
Comment #1
lars toomre commentedHere is an initial untested patch for this issue. Let's see what the testbot thinks.
Comment #2
robloachLooks reasonable. Think we should do a run through of the other files too?
Comment #3
lars toomre commentedYes, we probably should but the thought of opening up and checking each and every file in drupal core is overwhelming.
Are you aware of some tool or script that we could use that could identify all php files that do NOT start with?
That list of files would be the ones we need to address.
Comment #4
jhodgdonThe easiest way to find which files do not have @file directives would be to go to api.drupal.org, click on "Files" in the sidebar navigation, and scan the list for ones that don't have descriptions. Although api.d.o may not be totally up to date, it should get you 90% there at least
Comment #5
jhodgdonHowever, missing @file blocks should be taken care of anyway in the "Clean up API docs" issues, so I wouldn't think we need to scan every file for them on this issue.
Comment #6
jhodgdonAlso, this looks like it's changing both code and documentation, so changing component.
Comment #17
quietone commentedThis is now outdated and now that Committer checks added to DrupalCI tests for Drupal Core has happened there should be no regression.
Therefore, closing as outdated. If this is incorrect reopen the issue, by setting the status to 'Active', and add a comment explaining what still needs to be done.
Thanks!