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

Consider splitting type-aware linting from non-type-aware linting #112

Open
amannn opened this issue Nov 20, 2024 · 1 comment
Open

Consider splitting type-aware linting from non-type-aware linting #112

amannn opened this issue Nov 20, 2024 · 1 comment

Comments

@amannn
Copy link
Member

amannn commented Nov 20, 2024

Due to https://typescript-eslint.io/troubleshooting/typed-linting/performance/, it could be worth considering making type-aware linting rules not the default when using the typescript preset. This could also be used to run type-aware linting only on CI for example, without slowing down IDE performance.

@amannn
Copy link
Member Author

amannn commented Nov 20, 2024

Or actually, only this rule seems to be incredibly slow: @typescript-eslint/no-misused-promises.

We could either remove it or run it only on CI:

{
    rules: {
      '@typescript-eslint/no-misused-promises': process.env.CI ? 'error' : 'off'
    }
  }

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

No branches or pull requests

1 participant