-
-
Notifications
You must be signed in to change notification settings - Fork 392
-
-
Notifications
You must be signed in to change notification settings - Fork 392
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
Linter Product Plan and Progress #481
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Any plans to add eslint-plugin-perfectionist rules? It is becoming quite popular, 1.5 K stars. Just looking forward to fully migrate to amazing and promising OXC stack! |
This rule fits well in the formatter but not the linter. Its documentation says "I love Prettier. However, this is not his area of responsibility." But we are an integrated toolchain, things differ a little :-) So the answer to your question "Any plans to add eslint-plugin-perfectionist rules" is currently no, but it's doable once we have more manpower and also the formatter ready. |
Thanks! Hopefully after the OXC linter core will be ready, we will be able to use some AI tools to convert ESLint linters to OXC/Rust :) |
Appreciate your efforts. Your tool is incredible. Looking forward to use it.
Ready for testing to help you implement this (since i dont know Rust yet ;D) |
I would love love it if eslint-plugin-vue got added. Vue has to employ unique parsing for SFCs. |
very useful plugin for react dev time performance - eslint-plugin-react-refresh |
Product Plan
Create a linter that is
See also: Oxlint General Availability Annoucement
Plugins
For plugins, the goal is to port most of the popular ones. The community has implemented 270 rules and the list is growing. Any form of contribution is much appreciated!
Tasks
Contributing
oxc-project.github.io contains both learning materials and contribution guides:
Note
Oxlint does not implement any stylistic / formatting rules due to
The text was updated successfully, but these errors were encountered: