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 chai .not expectation would be super useful, for example:
-
name: 'listing hashes after removing'assertion: 'should not return the same hash'inputs:
pinlist: trueexpect:
out:
not:
contain: 'Qmctf39Vj8aLdg9icf2kvVcENyuNWBwy5TGWvHX9CZ6UkG'
I don't think we should attempt to chain / compose the expectations, that is kind-of a rabbithole. Very quickly one is inventing a whole programming language...
So I think we should just havenotFoo operators, for every Foo that we think make sense. In the implementation we can programatically generate them, if it makes sense.
The chai .not expectation would be super useful, for example:
Use case: the "listing hashes after removing" test in https://github.com/noflo/noflo-ipfs/blob/master/spec/Pin.yaml
The text was updated successfully, but these errors were encountered: