[valid-expect]: support specifying custom async matchers

[yatki]

A bit similar to #54, when we don't await .toReject(), the test returns false positive.

Maybe it's better to have a rule like await-async-matchers to cover all this cases.

[SimenB]

toReject is not part of Jest core, so I don't think built-in support makes sense. We can however maybe take some config either globally er per rule for asyncMatchers or some such?

[yatki]

Ah yes it was part of the jest-extended, wasn't it? Sorry for the issue then.

However, I really liked the idea of accepting a config parameter. What I understood from that is: I can add .toMyCustomMatcher() as an async matcher to my .eslintrc config and valid-expect rule or a new rule can make sure that those matchers are awaited.

Please let me know if it make sense this way, or did you mean something else?
🖖

[G-Rath]

Have made #1018 implementing this, with the jest-extended matchers as the default for the option.

[github-actions]

🎉 This issue has been resolved in version 25.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀