项目作者: bahmutov

项目描述 :
My custom eslint rules in addition to the ones provided at http://eslint.org/
高级语言: JavaScript
项目地址: git://github.com/bahmutov/eslint-rules.git
创建时间: 2014-11-24T13:48:45Z
项目社区:https://github.com/bahmutov/eslint-rules

开源协议:

下载


eslint-plugin-extra-rules

Additional rules for eslint

NPM

Build status
dependencies
devdependencies
semantic-release
manpm
renovate-app badge

Install

  1. npm install --save-dev eslint-plugin-extra-rules

Example Configuration

Add to your .eslintrc:

  1. {
  2. "plugins": ["extra-rules"],
  3. "rules": {
  4. "extra-rules/no-commented-out-code": "warn",
  5. // Your other rules...
  6. }
  7. }

Rules

no-commented-out-code

Detects code in the single or multiline comments

  1. /* eslint extra-rules/no-commented-out-code: "warn" */
  2. /*
  3. function foo() {
  4. return 'foo';
  5. }*/
  6. // this is normal comment
  7. function baz() {
  8. 'use strict';
  9. // and this is another normal comment
  10. // var bar = 'bar';
  11. return 'baz';
  12. }

Produces the following output:

  1. 2:0 warning commented out code "function foo() {" (4 lines) no-commented-out-code
  2. 10:2 warning commented out code "var bar = 'bar';" (1 line) no-commented-out-code

no-long-files

Detect source files with too many lines

  1. first argument: rule severity (0 - no check, 1 - warning, 2 - error)
  2. second argument: max number of allowed lines
  3. "no-long-files": [2, 70]

Prints something like

  1. potential-point-free.js
  2. 0:0 error file line count 51 exceeded line limit 50 no-long-files

camel_case

ESLint rule for enforcing camelCame names but allowing _ in property names

We want to use camelCase in variable names, but want to still allow
underscores in JSON objects:

  1. var goodObject = {
  2. property_name: 1,
  3. another_property: 2
  4. };

jshint has camelcase rule that forces EVERY name
to be camelCased

  1. $ jshint index.js
  2. index.js: line 2, col 0, Identifier 'property_name' is not in camel case.
  3. index.js: line 3, col 0, Identifier 'another_property' is not in camel case.
  4. 2 errors

There are manual workarounds:

  • disable this specific rule using // jshint ignore:lint or // jshint -W106
  • write property names using quotes, for example 'property_name': 1

Both workarounds are hacky.

I wrote a more flexible rule called camel_case
for eslint. The rule looks one character after
the identifier to see if it is followed by colon : character.
If yes, this is a property name inside an object, and underscore character _ is allowed.

no-for-loops

Warns or errors if you use for loops in your code. I consider for loops harmful for their side effects,
and even consider .forEach dangerous, see Avoid forEach.

no-single-line-objects

Does not allow you to nest objects into single line. Single property object can be single line

  1. // allowed
  2. var foo = { foo: 'foo' };
  3. // not allowed
  4. var foo = { foo: 'foo', bar: 'bar' };
  5. var foo = { foo: { bar: 'bar' } };

potential-point-free

Warns if a function just calls another function passing arguments and can potentially
become point-free. Point-free programming eliminates complexity and superfluous variables.
Only functions with single call expression are considered. The arguments must match exactly.

  1. /* eslint extra-rules/potential-point-free: "warn" */
  2. function print(x) {
  3. console.log(x);
  4. }
  5. [1, 2, 3].forEach(function printX(x) {
  6. print(x);
  7. });
  8. // output 7:18 warning printX potential-point-free

Note: due to signatures and optional arguments, sometimes functions should not be point free directly.
For example the array iterators pass item, index and the array itself, which causes problems for parseInt

  1. ['1', '2', '3'].forEach(parseInt);
  2. // [1, 'NaN', 'NaN']

In this case, you can use unary adaptor or
3rd party iterator with simpler signature, R.forEach.

Small print

Author: Gleb Bahmutov © 2014

License: MIT - do anything with the code, but don’t blame me if it does not work.

Spread the word: tweet, star on github, etc.

Support: if you find any problems with this module, email / tweet /
open issue on Github

MIT License

Copyright (c) 2014 Gleb Bahmutov

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the “Software”), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.