-
-
Notifications
You must be signed in to change notification settings - Fork 637
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
feat: exclude scripts with import errors #3285
Conversation
Caution Review failedThe pull request is closed. WalkthroughThe changes involve the modification of the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
jest.config.js (1)
5-7
: Approve changes with suggestions for improvementThe addition of
coveragePathIgnorePatterns
correctly implements the PR objective to exclude scripts with import errors from Jest coverage. However, consider the following suggestions:
The 'scripts/dashboard' path might be too broad. If you intend to exclude a specific file, consider using a more specific path (e.g., 'scripts/dashboard/specific-file.js').
Add a comment explaining why these files are excluded. This will help with future maintenance.
Since this is a temporary measure, consider adding a TODO comment to remind about resolving the import errors in the future.
Here's a suggested improvement:
module.exports = { verbose: true, collectCoverage: true, collectCoverageFrom: ['scripts/**/*.js'], + // TODO: Remove these exclusions once import errors are resolved coveragePathIgnorePatterns: [ - 'scripts/compose.js','scripts/dashboard' + 'scripts/compose.js', + 'scripts/dashboard/specific-file.js' // Replace with the specific file if applicable ], // To disallow netlify edge function tests from running testMatch: ['**/tests/**/*.test.*', '!**/netlify/**/*.test.*'], };
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3285--asyncapi-website.netlify.app/ |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3285 +/- ##
==========================================
+ Coverage 47.32% 49.14% +1.82%
==========================================
Files 22 21 -1
Lines 672 647 -25
==========================================
Hits 318 318
+ Misses 354 329 -25 ☔ View full report in Codecov by Sentry. |
@vishvamsinh28 What issue are you facing with import statements in those files, and why can it not be resolved now? |
@devilkiller-ag that issue comes under bounty program and @akshatnema told me not to write tests for them until someone fixes it |
/rtm |
This PR excludes 2 scripts from Jest code coverage until the import issue in them has been fixed.
Summary by CodeRabbit