Benjamin Kay

Appart from that, i would like to say i love this repo ;P

This has been sat here for a while, tbh I'm not sure how to go about this, nor how I feel about it either. I say this because I'm on...

okay, im happy to give this a go if nobody else wants to, are there any examples of async custom matchers knockin about? would make life easier, ill ofc have...

sweet cheers matt, enjoy your hols! 🏖

The logic of toHaveBeenCalledBefore is explicitly based on the first calls of the functions, However, this raises an interesting idea. May I suggest a more powerful matcher that can take...

you could always do the below to achieve the above ```js expect(mock1.mock.invocationCallOrder[0]).toBeLessThan(mock2.mock.invocationCallOrder[1]) ``` the mock function itself is core jest and not part of jest-extended and therefore probably not appropriate...

This sounds like a really good matcher and i would find it helpful myself :)

if nothing else im happy to raise a pr for this

Ive got a branch locally with a toHaveBeenCalledOnce matcher, it was queit straightforward, however the toHaveBeenCalledOnceWith is causing my brain issues, should we use === equality on objects or ==...

Sweet thank you @mattphillips, big help