feat(expect, @jest/expect): support type inference for toBe assertions
#13470
Conversation
royhadad
changed the title
toBe assertions
|
|
| expectType<void>( | ||
| expect({name: 'someName', age: 12}).toBe({name: 'someOtherName', age: 13}), | ||
| ); | ||
| expectError(expect({name: 'someName', age: 12}).toBe({name: 'someOtherName'})); |
There was a problem hiding this comment.
Hm.. But both of these will fail at run time, right?
There was a problem hiding this comment.
yep, both fail at run time
first one passes type checks
second one fails type checks
Changed the inverses to be unknown, I think this is good as this is the current behavior - so it should not do harm |
|
I see some failing tests in |
|
Closing because it's a duplicate of #13444 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
relates to #13334
This is a continuation of #13268, which was merged and reverted in #13339. It adds only one use case that should be safe.
It should improve developer experience by adding type inference for the types passed to the
toBeassertionTest plan
added automated tests
What do you guys think? @SimenB @mrazauskas