Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable more rules covered by TypeScript in the typescript config #3135

Open
FloEdelmann opened this issue Jan 2, 2025 · 1 comment
Open

Comments

@FloEdelmann
Copy link
Contributor

The typescript config already disables the import/named rule because it does not have an advantage over errors thrown by the TypeScript compiler:

// TypeScript compilation already ensures that named imports exist in the referenced module
'import/named': 'off',

There are some more rules that fall in the same category, which also typescript-eslint recommends to disable:

To avoid checking the same things the TypeScript compiler has already checked, I think it makes sense to also disable those rules (maybe except for import/no-unresolved) in the typescript config, so users don't have to (know and) disable them manually.

(It would also mitigate #2340 for TypeScript users.)

@soryy708
Copy link
Contributor

soryy708 commented Jan 8, 2025

What if the user is on an old version of TypeScript?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants