openstack
/
eslint-config-openstack
Code Issues Proposed changes
JavaScript Style Guidelines for OpenStack.
11 Commits 1 Branch 9 Tags 1.1 MiB
JavaScript 100%
Go to file
Michael Krotscheck 7f1592bfc0 Added npm default config. 
This patch adds an npmrc configuration file, which clears the
default version tagging prefix. This brings this project in line
with the standard tagging method used in openstack, rather than
'v1.0.0', it will use '1.0.0' as the tag. It also forces npm to
attempt to gpg-sign any tags created via `npm version`.

Change-Id: If7679f579b52633911bc5d6ee1f46dfae0104754
 		2015-08-18 14:45:23 -07: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
.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 Initial Commit 2015-06-23 18:40:37 -07:00
package.json Updated eslint version to 1.0.0 2015-08-06 16:30:44 -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