feat: show community take on the legacy post layout - #6507
Merged
Conversation
The community take only rendered inside PostFocusCard, which is gated by post_redesign — currently forced on for team accounts only. That made the surface invisible to everyone else even though community_sentiment is fully rolled out and the backend generates takes unconditionally. Render it in the legacy PostContent layout too, on the full post page only (matching the redesign, which hides it in the preview modal), with the same conditional enrollment so take-less posts don't dilute the split.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Problem
People reported not seeing community takes on posts that definitely have one.
The take is only rendered by
PostFocusCard, which is mounted only whenusePostRedesign().showRedesignis true. In GrowthBook,post_redesignhas prod defaultfalsewith a single force rule targeting{"team": 1}— so the surface is effectively team-only. Thecommunity_sentimentflag itself is fully on in prod and the API returnsPost.communitySentimentungated, so the data was there and just never rendered for anyone on the legacy layout.Change
Render
CommunitySentimentin the legacyPostContentlayout as well:isPostPage), matching the redesign which hides it in the preview modal via!onCloseuseConditionalFeatureenrollment oncommunity_sentiment, withshouldEvaluatebound to the post actually having a take so take-less posts don't dilute the treatment/control splitisDevelopmentescape hatch kept for local preview; the committed flag default staysfalseFrontend-only — generation is unconditional, no backfill needed.
Notes
!onClose/isPostPage).🤖 Opened by Smith (AI) on behalf of Chris.
Preview domain
https://feat-community-take-legacy-post.preview.app.daily.dev