Closed mroderick closed 1 year ago
I'm not sure if this should have a version bump at all
Patch and project coverage have no change.
Comparison is base (
b2a4df5
) 95.99% compared to head (5f7a468
) 95.99%.:exclamation: Current head 5f7a468 differs from pull request most recent head 832439d. Consider uploading reports for the commit 832439d to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Why not remove the threw
prop at the same time and clean it up? Or fix it? Now it is just left as historic scraps
Why not remove the threw prop at the same time and clean it up? Or fix it? Now it is just left as historic scraps
Using no argument spy.threw()
or with a named error type spy.threw("TypeError")
, threw
works as documented.
Since the introduction of threw in 0feec9ffba0da6bc2996cefa0c6e71872e8bedb2, no one have reported that
threw(obj)
doesn't work as the documentation states.Since it has been 12+ years without an error report, it's safe to assume that no one uses the
threw
method in this way. Let's remove it from the documentation.