refactor: Unify types for jest tsconfigs
#3298
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
network
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates TypeScript Jest configuration files to centralize and standardize the declaration of custom test utility types. The main change is moving the inclusion of
@streamr/test-utils/customMatcherTypesfrom package-level configurations into the roottsconfig.jest.json, ensuring all packages consistently include these types during testing.Changes
TypeScript Jest configuration updates:
@streamr/test-utils/customMatcherTypesto thetypesarray in the roottsconfig.jest.jsonso that custom matcher types are available project-wide.typesdeclarations frompackages/cli-tools/tsconfig.jest.jsonandpackages/trackerless-network/tsconfig.jest.jsonto rely on the centralized configuration. [1] [2]