chore: use .toBeCallableWith()
in type test
#2646
Open
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.
To draw attention, TSTyche 4 shipped with
.toBeCallableWith()
as well as.not.toBeCallableWith()
matchers.These can be used instead of
.toRaiseError()
to communicate the intent of the test much better. That also means there will be no red squiggles, because TypeScript will not detect any errors.If there any errors would appear in the type tests (try removing some
.not
), TSTyche will be loud and clear about that: