-
Notifications
You must be signed in to change notification settings - Fork 174
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
Support for React #148
Comments
Hi @newtack. Currently we're focusing on implementing as many rules from recommended set of ESLint and typescript-eslint. That said; React is super popular and at some point we're gonna implement those rules (or provide a way to do it via a plugin). |
This should be added only as a plugin. Otherwise the deno lint rule set will grow indefinitely, since React isn't eternal and there will come more frameworks. And even without support for frameworks, core rules should be added very carefully. Rules with little use case or possibility of being outdated should be added via a plugin system. Just look how ESLint ended up with 280 core rules! I really hope deno lint doesn't make the same mistake and delegates more rules to a plugin system. A recent blog post from the ESLint maintainers sums it up quite nicely: Changes to our Rules Policies |
@marvinhagemeister can we close this one with all the rules you added recently? |
There are a few more linting rules to add, but we're getting close. |
I love the promise of this project (linting, but fast).
We are using eslint not just for js/ts but also React specific rules (e.g. hooks, etc.).
Is this project eventually planned to support this?
The text was updated successfully, but these errors were encountered: