docs(expect): clarify the tolerance in toBeCloseTo
#6292
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6292 +/- ##
=======================================
Coverage 96.34% 96.34%
=======================================
Files 547 547
Lines 41661 41661
Branches 6313 6313
=======================================
+ Hits 40137 40138 +1
+ Misses 1482 1481 -1
Partials 42 42 ☔ View full report in Codecov by Sentry. |
kt3k
reviewed
Dec 23, 2024
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.
I was looking for a more pedestrian matcher, that would assert a number being within a range, or ±X of the expected value. Clarified
toBeCloseToas useful for avoiding floating point precision errors instead.