JavaScript Style Guidelines for OpenStack.
Go to file
Michael Krotscheck ed866bd401 Upgraded eslint to 1.10.3
This updates eslint to the newest version. This version does
not include new rules, only bugfixes for existing rules.

Change-Id: I73d8470ce01f3e1d68655d267d9ef9ee80ba47a5
2016-01-11 10:30:58 -08: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 version 2015-11-23 08:11:20 -08: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 1.10.3 2016-01-11 10:30:58 -08: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