openstack
/
eslint-config-openstack
Code Issues Proposed changes
JavaScript Style Guidelines for OpenStack.
9 Commits 1 Branch 9 Tags 1.1 MiB
JavaScript 100%
Go to file
Michael Krotscheck 92caba50a3 Relaxed eslint peer dependency 
Until we get proper dependency synchronization for javascript, it
makes more sense to use fuzzy peer dependencies. Relaxing this only
for peer dependencies means that this project remains stable,
however downstream consumers can set up their own versions.

Change-Id: I43896eaacd7d766c63ef71eec67e76ddca840089
 		2015-07-31 09:43:12 +10:00
spec Initial Commit 2015-06-23 18:40:37 -07:00
.editorconfig Initial Commit 2015-06-23 18:40:37 -07:00
.eslintrc Initial Commit 2015-06-23 18:40:37 -07:00
.gitignore Initial Commit 2015-06-23 18:40:37 -07:00
.gitreview Added gitreview file to project. 2015-07-09 11:05:51 -07:00
LICENSE Initial Commit 2015-06-23 18:40:37 -07:00
README.md Initial Commit 2015-06-23 18:40:37 -07:00
index.js Initial Commit 2015-06-23 18:40:37 -07:00
package.json Relaxed eslint peer dependency 2015-07-31 09:43:12 +10:00

README.md

eslint-config-openstack

OpenStack has a set of style guidelines for clarity. OpenStack is a very large code base, spanning dozens of git trees, with over a thousand developers contributing every 6 months. As such, common style helps developers understand code in reviews, move between projects smoothly, and overall make the code more maintainable.

Even though eslint permits overriding rules on a per-project basis, it should be the goal of every project to stay as close to the common guidelines as possible.

Installation

  1. npm install --save-dev eslint eslint-config-openstack
  2. Add extends: "openstack" to your .eslintrc