|
179 | 179 | "newlines-between": "never" |
180 | 180 | } |
181 | 181 | ], |
182 | | - "@typescript-eslint/ban-types": [ |
183 | | - "error", |
184 | | - { |
185 | | - "extendDefaults": false, |
186 | | - "types": { |
187 | | - "String": { |
188 | | - "message": "Use string instead", |
189 | | - "fixWith": "string" |
190 | | - }, |
191 | | - "Boolean": { |
192 | | - "message": "Use boolean instead", |
193 | | - "fixWith": "boolean" |
194 | | - }, |
195 | | - "Number": { |
196 | | - "message": "Use number instead", |
197 | | - "fixWith": "number" |
198 | | - }, |
199 | | - "Symbol": { |
200 | | - "message": "Use symbol instead", |
201 | | - "fixWith": "symbol" |
202 | | - }, |
203 | | - // "Function": { |
204 | | - // "message": "The `Function` type accepts any function-like value.\nIt provides no type safety when calling the function, which can be a common source of bugs.\nIt also accepts things like class declarations, which will throw at runtime as they will not be called with `new`.\nIf you are expecting the function to accept certain arguments, you should explicitly define the function shape." |
205 | | - // }, |
206 | | - "Object": { |
207 | | - "message": "The `Object` type actually means \"any non-nullish value\", so it is marginally better than `unknown`.\n- If you want a type meaning \"any object\", you probably want `Record<string, unknown>` instead.\n- If you want a type meaning \"any value\", you probably want `unknown` instead." |
208 | | - }, |
209 | | - "{}": { |
210 | | - "message": "`{}` actually means \"any non-nullish value\".\n- If you want a type meaning \"any object\", you probably want `object` or `Record<string, unknown>` instead.\n- If you want a type meaning \"any value\", you probably want `unknown` instead.", |
211 | | - "fixWith": "object" |
212 | | - } |
213 | | - // "object": { |
214 | | - // "message": "The `object` type is currently hard to use ([see this issue](https://github.com/microsoft/TypeScript/issues/21732)).\nConsider using `Record<string, unknown>` instead, as it allows you to more easily inspect and use the keys." |
215 | | - // } |
216 | | - } |
217 | | - } |
218 | | - ], |
219 | 182 | "@typescript-eslint/consistent-type-assertions": [ |
220 | 183 | "error", |
221 | 184 | { |
|
274 | 237 | "error", |
275 | 238 | { "ignoreArrowShorthand": true, "ignoreVoidOperator": true } |
276 | 239 | ], |
| 240 | + "@typescript-eslint/no-duplicate-type-constituents": "off", // Can't control `undefined` so its too noisy |
| 241 | + "@typescript-eslint/no-empty-object-type": ["error", { "allowInterfaces": "with-single-extends" }], |
277 | 242 | "@typescript-eslint/no-explicit-any": "off", |
278 | 243 | "@typescript-eslint/no-inferrable-types": ["warn", { "ignoreParameters": true, "ignoreProperties": true }], |
279 | 244 | "@typescript-eslint/no-invalid-void-type": "off", // Seems to error on `void` return types |
|
282 | 247 | "@typescript-eslint/no-redundant-type-constituents": "off", |
283 | 248 | "@typescript-eslint/no-unnecessary-condition": "off", |
284 | 249 | "@typescript-eslint/no-unnecessary-boolean-literal-compare": "off", |
| 250 | + "@typescript-eslint/no-unnecessary-type-parameters": "off", // https://github.com/typescript-eslint/typescript-eslint/issues/9705 |
285 | 251 | "@typescript-eslint/no-unsafe-argument": "off", |
286 | 252 | "@typescript-eslint/no-unsafe-assignment": "off", |
287 | 253 | "@typescript-eslint/no-unsafe-call": "off", |
|
291 | 257 | "@typescript-eslint/no-unused-vars": [ |
292 | 258 | "warn", |
293 | 259 | { |
294 | | - "args": "after-used", |
| 260 | + "args": "all", |
295 | 261 | "argsIgnorePattern": "^_", |
296 | | - "ignoreRestSiblings": true, |
297 | | - "varsIgnorePattern": "^_$" |
| 262 | + "caughtErrors": "all", |
| 263 | + "caughtErrorsIgnorePattern": "^_", |
| 264 | + "destructuredArrayIgnorePattern": "^_", |
| 265 | + "varsIgnorePattern": "^_", |
| 266 | + "ignoreRestSiblings": true |
298 | 267 | } |
299 | 268 | ], |
300 | 269 | "@typescript-eslint/no-use-before-define": ["error", { "functions": false, "classes": false }], |
|
0 commit comments