Alex J Burke

My apologies, I think I misread the value type to mean it wouldn't compare the error using satisfy semantics - the assertion does something a little special for strings I...

I've been thinking about this some more - I can definitely see the value in this alias but I'd like to raise one concern. Using satisfying here would introduce something...

Agreed about that spelling for which I think means we've reached some broad agreement - I can have a look next time I'm near core.

@papandreou it completely did and thought I'd mention I've brought this back to life :) Working on a small patch the records any pending promises in an array - but...

Oh and re stack trimming, you'll have to point me at where/how that's done as I'm not familiar with it.

This is really interesting - as it happens I recently did an experiment for the other part of this, which is to actually get auto-completion when writing assertions in test...

@sunesimonsen would you say this was actually replaced by all our error machinery, oathbreaker for sync workloads and returning promises in the case of async things?

I wonder if there is another option here - at some point as part of the `jest-unexpected` work I think I created a small bridge for `unexpected-sinon` to allow using...

@papandreou just nothing that a full implementation of that is available in jest-unexpected in case we want to crib anything. That said, I guess I'd lean on the side of...

@sunesimonsen could we alter the algorithm that processes assertions in the docs generator? What I was thinking is, for the list of available types, assertions we find supporting 'any' we...