Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 12 commits
- 12 files changed
- 6 contributors
Commits on Oct 2, 2025
-
feat: Reintroduce rule for prefer-called-exactly-once-with in alignme…
…nt with Vitest 3.0.0 (#772) * feat: add rule to prefer `toHaveBeenCalledExactlyOnceWith` over other matchers * test: add test * feat: add rule to prefer `toHaveBeenCalledExactlyOnceWith` * docs: add prefer-called-exactly-once-with doc
-
-
-
* prefer dynamic import in mock * prefer dynamic import in mock * add docs * add docs --------- Co-authored-by: Verité Mugabo <[email protected]>
-
Commits on Oct 5, 2025
Commits on Oct 6, 2025
-
Update prefer-called-exactly-once-with.md (#776)
The readme is a little in-exact, this change makes it more accurate.
Commits on Oct 12, 2025
-
fix(prefer-called-exactly-once-with): incorrect auto-fix behavior (#778)
* fix: replace toHaveBeenCalledOnce/With pairs with toHaveBeenCalledExactlyOnceWith * test: add tests * fix: fix build error
-
Commits on Oct 13, 2025
-
fix(prefer-called-exactly-once-with): detect mock resets between asse…
…rtions (#780) * fix: handle cases where mock is reset mid-test * test: add tests * fix: fix format
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.3.13...v1.3.18