JavaScript Style Guidelines for OpenStack.
Go to file
Michael Krotscheck 5bc48bf279 Upgraded eslint to 2.4.0
This upgrades the eslint version to 2.4.0, removes zombie rules,
and ensures that all new rules are disabled.

Change-Id: I6249663f8e226c5fa2739481b4c79625f94c7eb5
2016-03-16 08:08:50 -07:00
spec Enable strict 2015-09-22 10:24:59 -07:00
.editorconfig Initial Commit 2015-06-23 18:40:37 -07:00
.eslintrc Upgraded eslint to 2.4.0 2016-03-16 08:08:50 -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
.npmrc Added npm default config. 2015-08-18 14:45:23 -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 Stop using IIFE for index.js 2015-10-07 10:12:33 -07:00
package.json Upgraded eslint to 2.4.0 2016-03-16 08:08:50 -07: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