We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 3ade062 commit 9ddd667Copy full SHA for 9ddd667
.changeset/swift-pets-check.md
@@ -0,0 +1,16 @@
1
+---
2
+'@nullvoxpopuli/eslint-configs': patch
3
4
+
5
+Rule fixes which affect typescript and ember projects:
6
7
+in Ember projects, node files will be linted assuming at least Node 16.
8
+(Node 16 is already a requirement to use eslint-configs v3)
9
10
+in TypeScript projects, the "ban-types" lint has been turned off.
11
+In my experience writing libraries, there are many cases where
12
+"basic type and you just don't care, becausue it doesn't affect intellisense"
13
+is the right choice -- these types include `object` and `Function`,
14
+for example, and should be allowed.
15
+It's true that using different types that are more specific would provide better intellisense,
16
+if they are user facing -- but for non-user-facing types, these types are perfectly fine.
0 commit comments