'to yield exchange satisfying' not documented

[msiebuhr]

unexpected-express/lib/unexpectedExpress.js

Line 47 in 33d9d53

'<function> to yield exchange satisfying <any>', // Please prefer this one because it does use 'to satisfy' semantics

Comment says Please prefer this one because it does use 'to satisfy' semantics, so I guess it is important :)

[papandreou]

Damn, there isn't even a documentation site for unexpected-express. It's probably the plugin that I use most often myself, maybe except for unexpected-sinon. Skomagerens børn går i hullede sko...

[msiebuhr]

http://unexpected.js.org/unexpected-express/ was what I had in mind...

[papandreou]

Right, that's there, but there's no structured docs for the individual assertions (yet).

You're right, we should change the examples to use to yield exchange satisfying. If you have the time, the source is here: https://github.com/unexpectedjs/unexpected-express/blob/master/documentation/index.md

[joelmukuthu]

From the code, I'm guessing to yield exchange exhaustively satisfying is not supported?

[papandreou]

@joelmukuthu Correct! Have you found yourself needing that?

[joelmukuthu]

I'm introducing unexpected-express at my job and I'd like to make it possible to have exhaustive satisfactions for the new-comers (possibly to avoid omissions). I actually don't know how it would work, having to describe everything in the req/res but I just wanted to know if it's supported. Don't need it per se

[papandreou]

The exhaustiveness would only apply to the response part, as the request part is specifying the input, which per definition is exhaustive. Right?

[joelmukuthu]

Indeed, correct!

[papandreou]

Well, it would be a useful addition, and probably not very hard. PR welcome :)

[joelmukuthu]

Cool, will find some time to try it out :)