You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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?
🖖
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.The text was updated successfully, but these errors were encountered: