-
Notifications
You must be signed in to change notification settings - Fork 155
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
Remove Showkase processor not found warning from Danger #3148
Remove Showkase processor not found warning from Danger #3148
Conversation
dc2dc9e
to
482f166
Compare
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3148 +/- ##
========================================
Coverage 76.03% 76.03%
========================================
Files 1635 1635
Lines 38608 38608
Branches 7464 7464
========================================
Hits 29354 29354
Misses 5366 5366
Partials 3888 3888 ☔ View full report in Codecov by Sentry. |
aaad970
to
373ca5a
Compare
Instead create a new rule to check if the package name is included in `ComposablePreviewProvider`.
373ca5a
to
a6f9762
Compare
Quality Gate passedIssues Measures |
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.
LGTM, thanks!
Type of change
Content
Remove Danger check to ensure Showkase is enabled in modules with previews. Instead try to check if the package of the preview is in the list of packages to scan in
ComposablePreviewProvider
.Motivation and context
We don't use Showkase anymore for this.
Tests
The CI failed before when the new rule was broken: #3148 (comment)
Checklist