Jasmine matchers feature parity

[AmyBlankenship]

🚀 Feature Proposal

Use output from second parameter in matchers like in Jasmine.

Motivation

This lets me write efficient code but still know exactly which object had a mismatch.

Example

In Jasmine, I can do something like this:
for (var i=0, i<myObjects.length; i++) {
myObj = myObjects[i];
expect myObj.someprop.toEqual(1, index + ' ' + myObj.name);
}

Pitch

You're using Jasmine under the hood anyway--why would you make your matchers so much less capable than theirs?

[SimenB]

Duplicate of #3293

---

You're using Jasmine under the hood anyway--why would you make your matchers so much less capable than theirs?

We don't use jasmine's matchers

[AmyBlankenship]

Is there a way to use them with expect? Or could you fix yours to work better?

[SimenB]

No, they're not pluggable. You can use chai or the linked jest-expect-message, though

[AmyBlankenship]

Could you just fix yours?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.