-
Notifications
You must be signed in to change notification settings - Fork 24
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
Use shared vitest config and enable thresholdAutoUpdate for some packages. #1169
Conversation
🦋 Changeset detectedLatest commit: 3d5d02c The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Ignored Deployments
|
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.
Great!
28a1ff4
to
dcfb0eb
Compare
…enable threshold updater.
…able threshold updater.
…threshold updater.
… well as locally. Removing thresholdAutoUpdate for react-ui, for now.
eda126e
to
47c8be8
Compare
Currently vitest is configured to gather code coverage in CI as well as not run in watch mode. After various tests both of these do not seem to work correctly. This PR aims to fix this behaviour.
With this PR, all relevant packages now correctly depend on the shared vitest configuration and only override settings that are package specific. Code coverage is now collected again.
There are some packages that do not meet the globally defined criteria defined in the @kadena-dev/shared-config package. The current coverage levels have been set as baseline for these packages and ThresholdAutoUpdated has been enabled. As developers work to improve coverage, the baseline will be increased as well.
The following packages are impacted by this:
The result wil be that, gradually code coverage will be increased for packages that are touched often until they meet the globally defined defaults.