-
-
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
Roll up coverageThresholds set in project configs #6998
Comments
@rickhanlonii @SimenB anyone? This seems like something that should work with the |
@wldcordeiro sorry for the delay! This makes a ton of sense to me, are you interested in submitting the PR? |
@rickhanlonii I would be, I think I'd need some help though as I haven't done any coding in the Jest codebase before. General questions:
I want to get off on the right foot here and make things as easy for maintainer to review once I have a PR ready. |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🚀 Feature Proposal
Roll up the
coverageThresholds
config blocks fromprojects
to work like you had added the projects to thecoverageThresholds
paths.Motivation
Allowing users to configure their project thresholds individually and rolling up is a lot like what is already in place for configuring thresholds, only it would be more convenient with how projects are used.
Example
jest.config.js
packages/a/jest.config.js
packages/b/jest.config.js
Pitch
You can already go into your root configuration and define thresholds on a per path/file basis, this would be similar only it would allow for each package in a monorepo to define a threshold close to itself.
The text was updated successfully, but these errors were encountered: