[wp-trac] [WordPress Trac] #33655: WordPress Coding Standards (top level files)
WordPress Trac
noreply at wordpress.org
Tue Sep 1 21:41:56 UTC 2015
#33655: WordPress Coding Standards (top level files)
-------------------------+----------------------
Reporter: Compute | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: General | Version: trunk
Severity: normal | Resolution: wontfix
Keywords: | Focuses:
-------------------------+----------------------
Changes (by DrewAPicture):
* status: new => closed
* resolution: => wontfix
* milestone: Awaiting Review =>
Comment:
Hi @Compute,
As a matter of core philosophy, we don't refactor for the sake of
refactoring, even if means to only bring code in line with our coding
standards.
I don't know that I would consider the hook documentation effort to be a
valid parallel as we essentially introduced a great deal of new
documentation – for which we actually introduced a
[https://make.wordpress.org/core/handbook/best-practices/inline-
documentation-standards/php/ php inline documentation standard]. It's a
lot easier to do these things from the very beginning, unfortunately.
There's a very informative post about core philosophy on refactoring on
the core development blog that's worth a read:
https://make.wordpress.org/core/2011/03/23/code-refactoring/
Thanks for the suggestion.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33655#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list