feat(jest-expect): re-export Matchers
and MatcherFunctionWithState
interface
#12418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Perhaps
jest-expect
should re-exportMatchers
interface as well?I was looking at the example again. Feels like Jest users should be recommended to extend interfaces from'@jest/expect'
instead of'expect'
. Right? In this caseMatchers
must be re-exported fromjest-expect
.Also
MatcherFunctionWithState
is also useful. It is just the same asMatcherFunction
, but takes two generic type arguments (state and matcher args) instead of one (only matcher args). I guess in most of the casesMatcherFunction
will do the job, but for more advance usageMatcherFunctionWithState
will be helpful too.Other problem. Because of augmentation the example was pulling types from test type files. Ups.. I added minimal
tsconfig.json
, which helps to isolate the example.Test plan
Green CI.