JavaScript Style Guidelines for OpenStack.
Go to file
Michael Krotscheck a7c3268b79 Disable no-undefined
This disables the no-undefined rule. Most JavaScript projects in
OpenStack, at this point, have adopted eslint-config-angular, which
declares the 'definedundefined' rule requiring angular.isDefined()
or angular.isUndefined() to handle this case. That makes this
rule redundant, while also forcing non-production pieces of code
(such as unit tests) to become unnecessarily verbose.

https://github.com/Gillespie59/eslint-plugin-angular/blob/master/docs/definedundefined.md
http://eslint.org/docs/rules/no-undefined

Change-Id: I35ae5c8bc9e7ebb5c455d4acbe79636653448f65
2016-01-04 10:19:50 -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 Disable no-undefined 2016-01-04 10:19:50 -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 version 2015-11-13 06:54:36 -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