Add isSensitive prop to reader revenue components#15582
Merged
Conversation
…ayouts. - Standard, Showcase, Interactive, Immersive, Comment, Audio and LiveBlog. - Update tests to include the new required prop.
|
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
added 2 commits
March 25, 2026 09:46
Member
looks like this isn't relevant? |
tomrf1
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR threads the
isSensitivearticle property through the reader revenue component stack to enable sensitive content detection for epic and banner eligibility checks.Changes:
isSensitiveprop toLiveBlogEpic,SlotBodyEnd, and StickyBottomBanner componentsisSensitivein its decision dataSlotBodyEnd