-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: individualizing jest configs #714
Closed
Closed
Conversation
This file contains 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
Coverage report
Show files with reduced coverage 🔻
Test suite run success669 tests passing in 94 suites. Report generated by 🧪jest coverage report action from eaf5876 |
arboleya
force-pushed
the
aa/chore/individualizing-jest-configs
branch
from
January 1, 2023 12:43
11df7d5
to
eaf5876
Compare
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 PR does a couple of things:
<rootDir>/toolbox
workspace<rootDir>/toolbox/tests
packagejest.config.ts
configs for all packages (like we do fortsconfig.json
)This is the first small step towards a better organization for our repo-related tooling, which should provide a better SOC by segregating things that belong to the SDK (the
library
) from generalscripts
andutilities
intended to support the repo and its development cycle, while also targeting those building on Fuel (think about test utilities and whatnot).