@tim-code/eslint-config 1.1.4 → 1.1.5

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.
Files changed (2) hide show
  1. package/.eslintrc.js +4 -1
  2. package/package.json +1 -1
package/.eslintrc.js CHANGED
@@ -82,6 +82,10 @@ module.exports = {
82
82
  "dot-notation": ["error", { allowPattern: "^[A-Z]" }],
83
83
  // multi assign is confusing with declarations but non-declarations are okay
84
84
  "no-multi-assign": ["error", { ignoreNonDeclaration: true }],
85
+ // although using block style comments is easiest for writing a paragraph, JSDoc is usually preferred
86
+ // when writing such comments during brainstorming, just disable the rule
87
+ // most of the time, want to discourage non-JSDoc block style comments in production
88
+ "multiline-comment-style": "separate-lines",
85
89
 
86
90
  // unsure
87
91
  "no-labels": "off", // useful to be able to break/continue an outer loop; otherwise have to write more code
@@ -118,7 +122,6 @@ module.exports = {
118
122
  "max-classes-per-file": "off", // one class per file discourages small classes
119
123
  "lines-between-class-members": "off", // discourages smaller classes
120
124
  "guard-for-in": "off", // warning about language feature; reasons to avoid it are too theoretical: works fine in nearly all cases
121
- "multiline-comment-style": "off", // using block style comments is easiest for writing a paragraph
122
125
 
123
126
  // disabled too often
124
127
  "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.4",
3
+ "version": "1.1.5",
4
4
  "description": "",
5
5
  "main": ".eslintrc.js",
6
6
  "author": "",