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

This doesn't solve the problem #6

Closed
NikitaIT opened this issue Jan 16, 2024 · 1 comment
Closed

This doesn't solve the problem #6

NikitaIT opened this issue Jan 16, 2024 · 1 comment
Labels
question Further information is requested

Comments

@NikitaIT
Copy link

I had to add reportUnusedDisableDirectives:false to my eslint config to prevent autofix from removing comments.

reportUnusedDisableDirectives: false

In jest tests I always get a false positive eslint(no-undef).

The VSCode plugin is not configurable for some of the rules listed here. This is why I don't get any hints about typescript-eslint(no-explicit-any). It would be nice to separate the rules into those that are enabled by default and those that are not. Now, in order to disable something in eslint, I need to go through all the rules and check that they work. Unfortunately, right now I can't delegate part of the pipeline from eslint to oxlint for only one reason - I can't find out that oxlint is not working as expected until I run eslint.

Overall I really like the speed. But I still should turn off the rules explicitly.

@Dunqing
Copy link
Member

Dunqing commented Jan 18, 2024

Thank you for your feedback, Yes we should separate the rules because, Because in usually, people only use default rules

@Djiit Djiit added the question Further information is requested label Mar 6, 2024
@Boshen Boshen closed this as not planned Won't fix, can't repro, duplicate, stale Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants