Fix broken type definitions for extend-expect.d.ts #101
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.
What/Why: #93 introduced a regression into the TypeScript definitions. It used invalid TypeScript syntax and re-declared properties like
not
which conflict with@types/jest
. Errors for an empty TypeScript project:How: This PR fixes the types based on the intentions of the author of #93 and the types in
@types/jest
. Unfortunately, Jest does not provide better typings for matchers likeexpect.stringContaining('foo')
thanany
.https://github.com/DefinitelyTyped/DefinitelyTyped/blob/d17c14a550e68b0a1811afabd40677c7580f3579/types/jest/index.d.ts#L482
Checklist: