joepie91
/
pegjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
redux
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '26ded450f4'
${ noResults }
pegjs/.eslintrc.json

10 lines
133 B
JSON
Raw Normal View History Unescape Escape

Use ESLint instead of JSHint Implement the swap and change various directives in the source code. The "make hint" target becomes "make lint". The change leads to quite some errors being reported by ESLint. These will be fixed in subsequent commits. Note the configuration enables just the recommended rules. Later I plan to enable more rules to enforce the coding standard. The configuration also sets the environment to "node", which is far from ideal as the codebase contains a mix of CommonJS, Node.js and browser code. I hope to clean this up at some point.
9 years ago
{
Use eslint 3.2.0 Note the update required disabling the "no-control-regex" rule, which started reporting following errors: /Users/dmajda/Programming/PEG.js/pegjs/lib/compiler/js.js 22:16 error Unexpected control character in regular expression no-control-regex 27:16 error Unexpected control character in regular expression no-control-regex 28:16 error Unexpected control character in regular expression no-control-regex 51:16 error Unexpected control character in regular expression no-control-regex 52:16 error Unexpected control character in regular expression no-control-regex /Users/dmajda/Programming/PEG.js/pegjs/lib/parser.js 76:16 error Unexpected control character in regular expression no-control-regex 77:16 error Unexpected control character in regular expression no-control-regex 90:16 error Unexpected control character in regular expression no-control-regex 91:16 error Unexpected control character in regular expression no-control-regex
8 years ago
"extends": "eslint:recommended",
.eslintrc.json: Set parserOptions.ecmaVersion to 6 This means all code will be parsed as ES2015 by ESLint. See #442.
8 years ago
"parserOptions": {
"ecmaVersion": 6
},
Use eslint 3.2.0 Note the update required disabling the "no-control-regex" rule, which started reporting following errors: /Users/dmajda/Programming/PEG.js/pegjs/lib/compiler/js.js 22:16 error Unexpected control character in regular expression no-control-regex 27:16 error Unexpected control character in regular expression no-control-regex 28:16 error Unexpected control character in regular expression no-control-regex 51:16 error Unexpected control character in regular expression no-control-regex 52:16 error Unexpected control character in regular expression no-control-regex /Users/dmajda/Programming/PEG.js/pegjs/lib/parser.js 76:16 error Unexpected control character in regular expression no-control-regex 77:16 error Unexpected control character in regular expression no-control-regex 90:16 error Unexpected control character in regular expression no-control-regex 91:16 error Unexpected control character in regular expression no-control-regex
8 years ago
"rules": {
"no-control-regex": "off"
}
Use ESLint instead of JSHint Implement the swap and change various directives in the source code. The "make hint" target becomes "make lint". The change leads to quite some errors being reported by ESLint. These will be fixed in subsequent commits. Note the configuration enables just the recommended rules. Later I plan to enable more rules to enforce the coding standard. The configuration also sets the environment to "node", which is far from ideal as the codebase contains a mix of CommonJS, Node.js and browser code. I hope to clean this up at some point.
9 years ago
}