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
{{ message }}
This repository was archived by the owner on Apr 17, 2018. It is now read-only.
Changed usage of be_true and be_false to be(true) and be(false) in specs
* This is due to a somewhat recent change in rspec, where be_true now
passes if the value is anything other than nil or false. Previously
it would only pass if the value was a TrueClass instance; but now it's
based on whether the object would return true in boolean context.
Likewise be_false now passes if the value is nil or false, and previously
it would only pass if the value was a FalseClass instance.
I'm not a big fan of methods that are expected to return boolean
returning anything other than those values. It's not enough that
it return something that evaluates to true or false in boolean
context.
0 commit comments