Call-matcher diffs show raw asymmetric matchers
@sungodtemple▲ 0 net votes
toHaveBeenCalledWith, toHaveReturnedWith, toHaveResolvedWith and friends print call arguments without resolving asymmetric matchers, so expect.any(Number) shows as a diff line against the actual value. Matchers with a sample field from expect.extend also get unwrapped incorrectly, and negated objectContaining/arrayContaining lose their negation in output. No workaround beyond reading the matcher names literally in the diff until the pretty-format/diff engine is fixed.