-
-
Notifications
You must be signed in to change notification settings - Fork 443
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 oxlint disable directives #2999
Labels
A-linter
Area - Linter
C-enhancement
Category - New feature or request
good first issue
Experience Level - Good for newcomers
Comments
I didn't know eslint does this ... We can easily support this by changing the check here
PR is welcomed. |
@Boshen could I give this a shot? |
Sure |
Boshen
added a commit
that referenced
this issue
Apr 19, 2024
Boshen
added a commit
that referenced
this issue
Apr 19, 2024
I wanted to ship this asap 😅 |
My bad for not getting to it in time. |
@Boshen it is does not work. Example command is here ❯ time bunx oxlint --config ./packages/eslint-config-node/oxlintrc.json
× eslint(max-lines): File has too many lines (385).
╭─[packages/eslint-config-base/airbnb-rules.cjs:1:1]
1 │ // eslint-disable-next-line @eslint-community/eslint-comments/disable-enable-pair
· ▲
2 │ /* eslint-disable max-lines */
╰────
help: Maximum allowed is 160.
Finished in 6ms on 36 files with 96 rules using 8 threads.
Found 0 warnings and 1 error.
________________________________________________________
Executed in 100.39 millis fish external
usr time 70.47 millis 78.00 micros 70.39 millis
sys time 22.72 millis 353.00 micros 22.37 millis
airlight on master via ⬢ v22.4.0
❯ |
@Boshen issue still persists
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-linter
Area - Linter
C-enhancement
Category - New feature or request
good first issue
Experience Level - Good for newcomers
Currently oxc supports
eslint-disable(-next-line)
andeslint-enable(-next-line)
etc in comments. This is not always desirable for a project. For example, if the project does not use the same plugins in ESLint as the ones turned on in oxc, ESLint complains about the rules being unknown.I propose we support
oxlint-*
in addition to the eslint directives so that we can add these comments without getting ESLint madThe text was updated successfully, but these errors were encountered: