Enable Ton matchers in TypeScript when using expect
from @jest/globals
#31
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.
Ton custom matchers like
toHaveTransaction
were previously only available when using the globalexpect
. This PR adds full TypeScript support for projects that importexpect
explicitly from@jest/globals
.Changes
TonMatchers<R>
interface to avoid duplication.jest.Matchers<R>
(for traditional global usage).@jest/expect
'sMatchers<R>
(for explicitexpect
imports).'expect'
.Motivation
Modern Jest usage, especially in TypeScript projects, often relies on explicit imports like:
Without this update, consumers lose type safety for Ton-specific matchers unless they use the global
expect
, which can lead to confusion or unnecessary workarounds.Benefits
expect
via@jest/globals
.as any
casts.Checklist
yarn test
)yarn lint
)