8442d0103b
This rule ensures that parameters used to declare a loop, are modified
within the loop. If they are not, it is likely that this is an error.
Example:
while(foo) {
doSomething(foo);
}
http://eslint.org/docs/rules/no-unmodified-loop-condition
Change-Id: I8f5a0b2b1f48a9f93e0946c76c497e86a199f01e
|
||
|---|---|---|
| spec | ||
| .editorconfig | ||
| .eslintrc | ||
| .gitignore | ||
| .gitreview | ||
| .npmrc | ||
| LICENSE | ||
| README.md | ||
| index.js | ||
| package.json | ||
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
To add these rules to your project, follow these steps.
npm install --save-dev eslint eslint-config-openstack- Add
extends: "openstack"to your.eslintrcyaml file
Approval Policies
If you would like to contribute, please follow OpenStack's contribution guidelines.
Rules only land with consensus
Patches that activate, deactivate, or modify rules, should only be merged if a consensus of reviewers is reached. In this case, consensus means at least five +1 votes, with no -1 votes. Cores may not override and/or ignore -1 votes.
Library upgrades require two cores
Patches that upgrade eslint only require two core approvers to land. These patches should add new upstream rules in a deactivated state, and delete any deprecated rules.