@tim-code/eslint-config 1.1.1 → 1.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.eslintrc.js +3 -2
- package/package.json +2 -2
package/.eslintrc.js
CHANGED
|
@@ -63,8 +63,6 @@ module.exports = {
|
|
|
63
63
|
"no-empty-function": ["error", { allow: ["arrowFunctions"] }],
|
|
64
64
|
// function keyword is more readable in general but "fat arrow" is more concise; disables function(){} syntax
|
|
65
65
|
"func-style": ["error", "declaration", { allowArrowFunctions: true }],
|
|
66
|
-
// matches default IDE shortcut for multiline comments
|
|
67
|
-
"multiline-comment-style": ["error", "separate-lines"],
|
|
68
66
|
// default is 50 lines which is sometimes limiting with Prettier's formatting (parameter destructuring can take up 10 lines for example)
|
|
69
67
|
// adding comments or blanks should not trigger this warning
|
|
70
68
|
// doubled from 75 to allow almost all usages in pluto where it was commonly disabled
|
|
@@ -80,6 +78,8 @@ module.exports = {
|
|
|
80
78
|
"prefer-destructuring": ["error", { AssignmentExpression: { array: false } }],
|
|
81
79
|
// 300 lines is too low
|
|
82
80
|
"max-lines": ["error", { max: 600 }],
|
|
81
|
+
// allow bracket notation for capitalized keys, which are more likely to correlate with an object being used as a map
|
|
82
|
+
"dot-notation": ["error", { allowPattern: "^[A-Z]" }],
|
|
83
83
|
|
|
84
84
|
// unsure
|
|
85
85
|
"no-labels": "off", // useful to be able to break/continue an outer loop; otherwise have to write more code
|
|
@@ -116,6 +116,7 @@ module.exports = {
|
|
|
116
116
|
"max-classes-per-file": "off", // one class per file discourages small classes
|
|
117
117
|
"lines-between-class-members": "off", // discourages smaller classes
|
|
118
118
|
"guard-for-in": "off", // warning about language feature; reasons to avoid it are too theoretical: works fine in nearly all cases
|
|
119
|
+
"multiline-comment-style": "off", // using block style comments is easiest for writing a paragraph
|
|
119
120
|
|
|
120
121
|
// disabled too often
|
|
121
122
|
"no-console": "off", // console error was already allowed; when is console.log actually bad?
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tim-code/eslint-config",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.3",
|
|
4
4
|
"description": "",
|
|
5
5
|
"main": ".eslintrc.js",
|
|
6
6
|
"author": "",
|
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
"eslint-config-prettier": ">= 9"
|
|
10
10
|
},
|
|
11
11
|
"peerDependencies": {
|
|
12
|
-
"eslint": ">=
|
|
12
|
+
"eslint": ">=8 <9",
|
|
13
13
|
"eslint-plugin-import": ">= 2"
|
|
14
14
|
},
|
|
15
15
|
"publishConfig": {
|