[buddypress-trac] [BuddyPress Trac] #5638: Introduce .editorconfig to BuddyPress

buddypress-trac noreply at wordpress.org
Wed May 14 05:59:08 UTC 2014

#5638: Introduce .editorconfig to BuddyPress
 Reporter:  netweb       |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Core         |    Version:
 Severity:  normal       |   Keywords:  has-patch
 Configuring your editor/IDE for submitting code/patches to BuddyPress and
 follow the code styling guidelines of BuddyPress is not the simplest of

 Via http://editorconfig.org
 > "EditorConfig helps developers define and maintain consistent coding
 styles between different editors and IDEs. The EditorConfig project
 consists of a file format for defining coding styles and a collection of
 text editor plugins that enable editors to read the file format and adhere
 to defined styles. EditorConfig files are easily readable and they work
 nicely with version control systems."

 Particularly as WordPress has now implemented this via #WP26429 if your
 editor or IDE supports this and you checkout the BuddyPress repo into a
 folder contained within the WordPress develop repo the default is to
 inherit all the rules from the upstream `.editorconfig`.

 To this end BuddyPress should include an `.editorconfig` file to
 explicitly declare it's own code styling guidelines or the same
 `.editorconfig` file as WordPress to use their `.editorconfig` rules.

 I just came across this whilst creating a patch for the BuddyPress
 `package.json` file, WordPress uses 'spaces' for tab indentation whereas
 BuddyPress are using `tabs`. I quickly fudged the WordPress
 `.editorconfig` file to match BuddyPress' so I could create a patch for
 `package.json` to match the current whitespace format.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5638>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list