You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(oxlint.config): spread the vitest recommended rules instead of listing them - #11942
The test-file override in oxlint.config.ts listed the @vitest/eslint-plugin recommended rules by hand, so it wouldn't follow changes to the plugin's recommended set.
Spread pluginVitest.configs.recommended.rules instead, then apply only the overrides: consistent-test-it, no-standalone-expect (with itIf), and valid-expect (native vitest/valid-expect off, vitest-js/valid-expect on, since the native rule doesn't check expectTypeOf).
This matches the structure of the previous ESLint config. The resulting rules are unchanged, and test:oxlint output is the same in every package.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Reviewing files that changed from the base of the PR and between df78a9d and dba94dd.
📒 Files selected for processing (1)
oxlint.config.ts
________________________________________________________
< Maybe I am just like my mother. She's never satisfied. >
--------------------------------------------------------
\
\ (\__/)
(•ㅅ•)
/ づ
✨ Finishing Touches📝 Generate docstrings
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Changes
The test-file override in
oxlint.config.tslisted the@vitest/eslint-pluginrecommended rules by hand, so it wouldn't follow changes to the plugin's recommended set.pluginVitest.configs.recommended.rulesinstead, then apply only the overrides:consistent-test-it,no-standalone-expect(withitIf), andvalid-expect(nativevitest/valid-expectoff,vitest-js/valid-expecton, since the native rule doesn't checkexpectTypeOf).test:oxlintoutput is the same in every package.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact