Postponed
Project:
Drupal core
Version:
main
Component:
other
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Jun 2017 at 16:17 UTC
Updated:
20 Oct 2025 at 06:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
vegantriathleteComment #3
cilefen commentedHi @vegantriathlete:
Thanks for suggesting this improvement. Check out the parent issue—standards fixes are done for all of core and also must come with a phpcs rule. I think in this case there may be no such rule yet.
Comment #4
chi commentedCould you please add a reference on documentation about this. Do we have officially approved coding standard for this?
Comment #5
vegantriathlete@Chi: As it turns out I don't think there is an official standard about how to order use statements. I think that I got the idea that there was one when I submitted a patch for a different module and the maintainer told me to sort my use statements alphabetically.
Comment #6
chi commented@vegantriathlete That means there is notihng to fix here.
The documetnation says:
Feel free to submit a proposal for this subject.
https://www.drupal.org/project/coding_standards
Comment #7
cilefen commentedComment #8
jonathan1055 commentedRe-opening this now that the work is nearing completion in #1624564: Coding standards for "use" statements and the modification #3470716: Configure use-statement sniff to be case sensitive is in Coder 8.3.25, released on 22 Sept.
As of 5 October Core 11.x is still running Coder 8.3.24, but when it uses Coder 8.3.25 work can be started on fixing the files.
Comment #9
longwaveWe should upgrade Coder in this issue and fix the use statements at the same time, in both 11.x and 10.4.x. This might be disruptive enough to existing patches to wait for the beta window, but we can certainly start now.
Comment #10
damienmckennaLet's postpone this issue until the coding standards issue is completed.
Comment #11
quietone commented