-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Add support for custom dependency extractors #7313
Add support for custom dependency extractors #7313
Conversation
2b85c59
to
37144a7
Compare
37144a7
to
933b451
Compare
933b451
to
f5c65f9
Compare
Codecov Report
@@ Coverage Diff @@
## master #7313 +/- ##
==========================================
- Coverage 66.64% 66.63% -0.02%
==========================================
Files 241 241
Lines 9337 9334 -3
Branches 5 6 +1
==========================================
- Hits 6223 6220 -3
Misses 3111 3111
Partials 3 3
Continue to review full report at Codecov.
|
Oh, awesome! I actually started a branch with this stuff months ago, but never was able to finish it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, integrating non-js runners is gonna be way better now.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Adds a new
dependencyExtractor
option to use a custom function to extract dependencies from the code. It will allow users to implement support for custom functions loading modules (which will be taken into account to determine which tests to run):package.json
:dependencyExtractor
:sample-test.js
:Test plan
Updated unit tests for the
jest-haste-map
and added an E2E test for this feature.