Skip to content

Commit 9aeceec

Browse files
fix: disable rule "new-cap"
This rule is implemented in a not very nice way when it comes to working with 3rd parties.
1 parent da58a0e commit 9aeceec

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

src/builtin/stylistic-issues.ts

+2-1
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,8 @@ export const rules: Linter.Config["rules"] = {
9494
"max-statements-per-line": ["error", { max: 1 }],
9595
"multiline-comment-style": "off",
9696
"multiline-ternary": ["error", "always-multiline"],
97-
"new-cap": ["error", { newIsCap: true, capIsNew: true }],
97+
// This rule is implemented in a not very nice way when it comes to working with 3rd parties.
98+
"new-cap": "off",
9899
"new-parens": "error",
99100
"newline-per-chained-call": [
100101
"error",

0 commit comments

Comments
 (0)