The uses sorting sniff has been reverted out of coder by default, but it can still be optionally enabled.
📌
Revert case sensitive use-statement sniff
Active
Use ordering enforcement is important on a project with disparate contributors to avoid any automated tools or IDE ping-ponging back and forth about the ordering. With a standard enforced on the MR, that will be the standard that code must meet.
Not yet a coding standard, but in the works, pending phpstorm fixing their auto-uses.
📌
Coding standards for "use" statements
RTBC
Without adding the sniff, ordering is not checked or enforced.
Add a use in the wrong order and commit it. It will not be picked up by phpcs.
Enforce a known ordering during testing.
Add phpcs.xml with expected standards.
n/a
n/a
n/a
NB: Will not trigger a release on its own.
Active
2.1
Testing
Won't change functionality of the module so have merged this one in. Looking forward to it being the default again so I don't end up getting another patch with one line of code changed lost amongst pages of use re-ordering diffs. Not on this project thankfully, but once is enough.
Automatically closed - issue fixed for 2 weeks with no activity.