feat(linter/eslint-plugin-vitest): Add prefer-to-contain as vitest compatible jest rule#16836
Merged
camc314 merged 1 commit intooxc-project:mainfrom Dec 14, 2025
Conversation
…mpatible jest rule
github-actions
bot
added
A-linter
CodSpeed Performance ReportMerging #16836 will not alter performanceComparing Summary
Footnotes
|
camc314
approved these changes
Dec 14, 2025
Member
|
lol was about to review and ask for the usual "compatible with vitest" note to the rule docs for this one :) We can do that in a follow-up PR though. |
graphite-app bot
pushed a commit
that referenced
this pull request
Dec 14, 2025
…_contain rule documentation (#16838) Corrects documentation typo in the `jest/prefer-to-contain` rule and adds vitest compatibility information. **Changes:** - Fixed typo in rule documentation: `TThis rule triggers` → `This rule triggers` - Added vitest compatibility note with configuration example showing how to enable `vitest/prefer-to-contain` in `.oxlintrc.json` The vitest compatibility note follows the same format as other vitest-compatible rules in the codebase and includes a link to the eslint-plugin-vitest documentation. <!-- START COPILOT CODING AGENT SUFFIX --> <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > action this PR review comment #16836 (comment) </details> <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/oxc-project/oxc/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Related to #4656
Add
prefer-to-containas a vitest compatible ruleOxlint-migrate PR: oxc-project/oxlint-migrate#280