[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 netweb):

 Replying to [comment:9 nacin]:
 > If no erroneous whitespace was detected across 79 files, then these
 rules must not be very strict. :-) Yeah, tabs, line endings, etc., are all
 going to be just fine across WordPress.
 Yes, I am quite sure most of WordPress' codebase will be fine as these
 rules are only the basic tabs, line endings rules etc

 Asking a 'new contributor' to adhere to the WP coding standards and
 configuring their text editor/IDE per
 http://make.wordpress.org/core/handbook/coding-standards/, then digging
 into each HTML, PHP, JS & CSS sections to just get 'the basics' up and
 running is quite daunting, it was for me so this is the context I proposed
 this.

 There is a section on the
 [https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties
 #wiki-ideas-for-domain-specific-properties .editorconfig wiki] on future
 'domain specific' ideas such as `spaces_around_operators`,
 `spaces_around_brackets` & `indent_brace_style` that could be looked at,
 it's the first time just now I've seen these 'proposed'.

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