<a href="https://github.com/type-eslint/type-eslint/blob/master/packages/e

add no-explicit-any about eslint-config-xo-typescript HOT 1 CLOSED

xojs commented on June 3, 2024

add no-explicit-any

from eslint-config-xo-typescript.

Comments (1)

EdJoPaTo commented on June 3, 2024 1

eslint-config-xo-typescript/index.js

Lines 295 to 304 in 72fbc20

 // TODO: Try to enable this again in 2022. 

 // Disabled for now. This is a great rule. It's just that TypeScript is not good enough yet to not use `any` in many places. 

 // For example: https://github.com/sindresorhus/refined-github/pull/2391#discussion_r318995182 

 // '@typescript-eslint/no-explicit-any': [ 

 // 'error', 

 // { 

 // fixToUnknown: true, 

 // ignoreRestArgs: true 

 // } 

 // ],

from eslint-config-xo-typescript.

Related Issues (20)

unicorn/prefer-json-parse-buffer is incompatible with TypeScript
@typescript-eslint/naming-convention should ignore all exotic keys HOT 1
Enable `@typescript-eslint/consistent-type-definitions` rule HOT 2
Use `eslint-import-resolver-typescript` instead of `eslint-import-resolver-node`? HOT 1
should `@typescript-eslint/parser` be listed in peer dependencies? HOT 1
Drop `@typescript-eslint/consistent-type-definitions` rule HOT 4
Update rule to prefer `import {type X}` over `import type {X}` HOT 2
Configuration for rule "@typescript-eslint/consistent-type-imports" is invalid: Value {"fixStyle":"inline-type-imports"} should NOT have additional properties. HOT 1
Invalid configuration for `@typescript-eslint/member-ordering`
Don't disable unicorn/no-null?
Consider enabling `strict-boolean-expressions`? HOT 1
Change `parserOptions.jsx` to `parserOptions.ecmaFeatures.jsx`?
Upgrade `@typescript-eslint/eslint-plugin` dependency to `5.45.0` minimum. HOT 1
Invalid configuration for `@typescript-eslint/restirct-plus-operands`
Invalid configuration for `@typescript-eslint/no-restricted-imports`
Off `import/named`
Disable the `import/no-duplicates` rule HOT 1
Consider disabling `default-case` because of `@typescript-eslint/switch-exhaustiveness-check`
Conflicts with @typescript-eslint libraries
`switch-exhaustiveness-check` config mismatch? HOT 3

add no-explicit-any about eslint-config-xo-typescript HOT 1 CLOSED

Comments (1)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	// TODO: Try to enable this again in 2022.
	// Disabled for now. This is a great rule. It's just that TypeScript is not good enough yet to not use `any` in many places.
	// For example: https://github.com/sindresorhus/refined-github/pull/2391#discussion_r318995182
	// '@typescript-eslint/no-explicit-any': [
	// 'error',
	// {
	// fixToUnknown: true,
	// ignoreRestArgs: true
	// }
	// ],