You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The previous implementation was to `assert(!value)` which led to
confusing failure messages when using `refute` directly.
For custom failure messages, `!value` is always `false` on failure, so
`false` is passed to the custom message block where the caller might
instead expect the value that caused the failure.
Similarly, the default failure message is always "expected false to be
truthy" when really the expectation is that something truthy is falsy.
0 commit comments