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

linter: jest and vitest compatible rules are reported as not supported #7240

Closed
Sysix opened this issue Nov 11, 2024 · 1 comment · Fixed by #7567
Closed

linter: jest and vitest compatible rules are reported as not supported #7240

Sysix opened this issue Nov 11, 2024 · 1 comment · Fixed by #7567
Labels
A-linter Area - Linter C-bug Category - Bug

Comments

@Sysix
Copy link
Contributor

Sysix commented Nov 11, 2024

What version of Oxlint are you using?

0.11.1

What command did you run?

npx oxlint -c .oxlint.json

What does your .oxlint.json config file look like?

{
  "categories": {
    "correctness": "off"
  },
  "rules": {
    "no-identical-title": "error",
//    "vitest/no-identical-title": "error", -- also report jest/no-identical-title not supported
//    "jest/no-identical-title": "error"  -- also reports jest/no-identical-title not supported
  }
}

What happened?

  ! The following rules do not match the currently supported rules:
  | jest/no-identical-title

The same does happend for other rules rules jest/no-focused-tests. I think all current rules are effected which should be the following:

  'consistent-test-it',
  'expect-expect',
  'no-alias-methods',
  'no-conditional-expect',
  'no-conditional-in-test',
  'no-commented-out-tests',
  'no-disabled-tests',
  'no-focused-tests',
  'no-identical-title',
  'no-restricted-jest-methods',
  'no-test-prefixes',
  'prefer-hooks-in-order',
  'valid-describe-callback',
  'valid-expect',
@dennis-meitner
Copy link

I'm seeing the same issue with 0.11.1 but with the following:

  • import/named
  • import/no-duplicates
  • import/no-extraneous-dependencies
  • import/default
  • import/namespace
  • import/first

Boshen pushed a commit that referenced this issue Nov 13, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 17, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 18, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
Dunqing pushed a commit that referenced this issue Nov 18, 2024
- related to #6988

This is causing a lot of errors currently such as
#7233. I think we need to
handle rule names more robustly first:

- #7240
- #7082
- #7242

then, I think we can revisit this and maybe implement it as an actual
lint plugin too? #7086
@Boshen Boshen closed this as completed in 810671a Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter C-bug Category - Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants