Enable to type t.context
by extending module interface
#3362
+17
−1
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.
Thank you for the great tool.
Summary
This Pull Request introduces a new AvaContext interface that can be augmented by library users. By allowing developers to declare custom fields in their test context, this change provides greater flexibility and type safety when writing tests in TypeScript.
Details of Changes
AvaContext
interfaceTestFn
to default its genericContext
toAvaContext
Library users can now directly extend the
AvaContext
interface to add custom properties in tests, which could be impressive when using shared context:Difference between
TestFn
There is already a guide to type
t.context
:This PR provides another method to type the context without creating a new variable, which make users ease to use context values.