-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 an article exclusion list to Billboards #19280
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #19280 +/- ##
==========================================
+ Coverage 88.73% 88.75% +0.01%
==========================================
Files 1175 1175
Lines 26389 26413 +24
Branches 2027 2028 +1
==========================================
+ Hits 23417 23442 +25
+ Misses 2818 2817 -1
Partials 154 154
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Uffizzi Preview |
Overall LGTM. I'll hold off from an official review to make sure this gets plenty of additional eyeballs. |
Co-authored-by: Ben Halpern <bendhalpern@gmail.com>
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.
@jaw6 this looks good and sound to me ✨ Thanks! Left two small bits of feedback.
Co-authored-by: Ridhwana <Ridhwana.Khan16@gmail.com>
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.
I was auto-requested for review here, but don't have the context necessary to really give this a deep business logic review, so consider my approval fairly gentle. My lone comment that can actually be acted on is optional/somewhat of a conversation piece more than anything.
Enabled: true | ||
Max: 15 | ||
StyleGuide: https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/ExampleLength | ||
Enabled: false |
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.
Nit: this diff, in my mind, feels like a separate PR to some degree, but I also acknowledge that this becomes Rebase Hell after a while, so I'm somewhat leaving this comment to learn the team philosophy around stuff like this.
(I see it's already its own commit with 85ed451, so git cherry-pick
onto a new branch, and maybe git commit --amend
to do some rewording, and that could be made standalone)
}, | ||
required: %w[name body_markdown placement_area] | ||
} | ||
parameter name: :display_ad, in: :body, schema: { type: :object, |
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.
Nothing to do with your work in this file, just the fact that this file exists at all is pretty neat - I love this "autogenerate the JSONSchema from real enum hashes" approach.
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.
Gave this another pass, it all looks good, and verified the functionality locally and in Uffizzi.
What type of PR is this? (check all applicable)
Description
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
https://www.loom.com/share/aa40a1d49ff949f590012d7268e999c3
Added/updated tests?
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
Storybook (for Crayons components)
updated. I have filled out the
Changes Requested
issue template so Community Success can help update the Admin Docs
appropriately.
CHANGELOG.md
or in a forem.dev post
replace this line with details on why this change doesn't need to be
shared
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?