-
Notifications
You must be signed in to change notification settings - Fork 26
Story 2296: V3 Post Detail page #2373
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
Open
julioest
wants to merge
28
commits into
boostorg:develop
Choose a base branch
from
julioest:feat/v3-post-detail-2296
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
e44666a
Story 2296: V3 Post Detail page
julioest 0294b8e
feat: text_paragraphs filter for post bodies
julioest 293a83f
style: V3 post detail visuals to match Figma
julioest 118a493
feat: wire V3 post author role and badge
julioest 9428b72
feat: pass description on V3 post-card data
julioest 7db8b8a
fix: add aria-label to V3 post external URL link
julioest 29b6a4e
style: V3 post detail mobile + tablet spacing
julioest 35fd291
style: V3 post-header date format m/d/Y
julioest dbc1e53
fix: use --font-code token in V3 post body
julioest 30df4f6
fix: pluralize Related Posts heading
julioest 433b601
style: V3 post-detail card and profile gaps
julioest 09d63aa
fix: tighten V3 post-detail mobile padding
julioest a36a832
fix: exclude deleted entries from V3 next/related
julioest 92f8977
fix: stable next/related order and deleted notice
julioest 4103cd6
refactor: extract user_profile_card helper
julioest 2b01c95
fix: preserve list and signoff breaks in posts
julioest f294e5a
refactor: V3 detail reuses /news/entry route
julioest 6714d65
fix: V3 post header date format and trim blank line
julioest 71de469
fix: V3 post title uses letter-spacing-tight token
julioest 5228655
fix: V3 post card uses category key with tag label
julioest b7f47e9
fix: V3 registry surfaces opted-out subclasses
julioest f7b8b60
fix: V3 post detail renders body as markdown
julioest e56ef83
chore: trim redundant CSS in post-detail body
julioest 666f824
fix: post-card dates render in written form
julioest 8f234ef
chore: rename TAG_LABELS to CATEGORY_LABELS
julioest ad08b2f
fix: post-card dates use 3-letter month abbreviation
julioest 70a710f
Lazy-load the post detail hero image
julioest a9431e7
Note related-posts library-scoping intent
julioest File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Hmm I think the next post should actually be the one relative to the current one, otherwise it'll always show the most recent post for all posts
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.
So, I dug into this a bit so I can better understand. I ran the same queryset in the dev shell with full timestamps. The query does return the chronologically next post, not the most recent overall.
The 2023-10-27 cluster makes it clear: five posts within ~40 minutes, each pointing at the next neighbor by timestamp.
This direction matches v2's
get_next_by_publish_at, so this feels more like a design call than a bug. Happy to flip it either way though.Let us know whatcha think @henryajisegiri
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.
Hey @julioest we can leave this for the integration ticket then. Thanks a ton for the digging. Henry is also aware we're leaving this for later.