feat(prefer-expect-assertions): support basic uses of hasAssertions in beforeEach and afterEach hooks
#1871
+1,125
−35
Conversation
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
G-Rath
force-pushed
the
support-before-assertions
branch
from
2b42d99 to
776c593
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Dec 13, 2025
# [29.3.0](v29.2.3...v29.3.0) (2025-12-13) ### Features * **prefer-expect-assertions:** support basic uses of `hasAssertions` in `beforeEach` and `afterEach` hooks ([#1871](#1871)) ([eed9acb](eed9acb))
|
🎉 This PR is included in version 29.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The implementation feels a bit rough, but it should be easy to build on - part of me wonders if it would be worth spitting the rule up into a rule for checking validate usage, and another for actually enforcing usage 🤔
Resolves #876