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

Prevent the use of any #251

Open
Gudahtt opened this issue Nov 11, 2022 · 3 comments
Open

Prevent the use of any #251

Gudahtt opened this issue Nov 11, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@Gudahtt
Copy link
Member

Gudahtt commented Nov 11, 2022

These lint rules would help prevent the use of any:

'@typescript-eslint/no-unsafe-argument': 'off',
'@typescript-eslint/no-unsafe-assignment': 'off',
'@typescript-eslint/no-unsafe-call': 'off',
'@typescript-eslint/no-unsafe-member-access': 'off',
'@typescript-eslint/no-unsafe-return': 'off',

We should consider enabling them to improve type safety.

@Gudahtt Gudahtt added the enhancement New feature or request label Nov 11, 2022
@Mrtenz
Copy link
Member

Mrtenz commented Nov 13, 2022

When we do this, we should also enable @typescript-eslint/no-explicit-any.

@mcmire mcmire changed the title Consider preventing the use of any Prevent the use of any Apr 11, 2023
@mcmire
Copy link
Contributor

mcmire commented Dec 5, 2023

Should we go ahead and enable these rules? Projects can feel free to disable these rules if they wish and add them back when there is time. Or should we audit existing projects to see how many would violate these rules?

@MajorLift
Copy link

Seconded on enabling the rules first to slow the rate of new any types being introduced into our codebases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants