[wp-trac] [WordPress Trac] #26429: Introduce .editorconfig to WordPress

[WordPress Trac]

#26429: Introduce .editorconfig to WordPress
------------------------------+------------------------------
 Reporter:  netweb            |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  3.8
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by jorbin):

 I like this idea.  Anything that helps ensure we only add new code that is
 in our guidelines is a good thing.

 My question is if any editors will interpret this file and attempt to make
 changes to our areas of our code base for the lines not directly edited?
 We generally avoid whitespace only changes as they make it harder to find
 meaningful change sets.  To quote Nacin
 [http://make.wordpress.org/core/2011/03/23/code-refactoring/ “Code
 refactoring should not be done just because we can.”]

 I do wonder if we can perhaps combine all of the various file types into
 the top [*]. We use tabs everywhere.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26429#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform