Skip to content

Open replies from the replies button, five at a time - #91

Merged
simonhamp merged 1 commit into
mainfrom
feat/open-replies
Oct 26, 2026
Merged

simonhamp merged 1 commit into
mainfrom
feat/open-replies

Conversation

@simonhamp

@simonhamp simonhamp commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

Three changes to how replies open, all on the commit page.

The replies button now opens the commit with its replies showing. Where a thread can't open in place (a reply's "N replies" on a commit page, notifications, an ancestor's row), the button now lands on the commit with the replies already expanded. "Show more" under a thread opened in a feed does the same.

The app asks for five replies at a time, never more. devnull sends 50 a page unless asked for fewer, so Client now adds limit=5 to every GET of commits/{id}/replies. The limit isn't part of the response cache key, so the cache's existing patches for new and deleted replies still find the entry. "Show more" loads the next five on the commit page. A deleted reply's replies, opened in place, now page too, with their own "Show more", because a deleted commit has no page to send you to. In a feed, a thread opened in place shows five, and "Show more" opens the commit page.

While doing this I hit a refresh bug that five a page makes common: once you'd loaded every page, coming back to the commit dropped everything after the first page and showed "Show more" again. Pages loaded after the first now stay (withFirstPage() in CommitDetail).

A reply's page shows its parent. The commit it replies to now sits above it. Only the ones before that fold behind "N earlier commits". A part of a series shows the part before it the same way, since that's its parent too.

Things to look at:

  • With a deleted reply that has more replies of its own and is also the last reply on the page, its "Show more" comes first. The page's own "Show more" appears once its replies are all loaded.
  • Tapping into the reply bar still folds the earlier commits away, but the parent stays, so the commit is second on the page, not first.

Screenshots

To follow: I'll add iOS and Android, light and dark, once the app is running from this branch.

  • No visible change

🤖 Generated with Claude Code

The "N replies" button, where a thread can't open in place (a reply on a
commit page, notifications and the like), now opens the commit with its
replies already showing. "Show more" under a thread opened in a feed does
the same.

The app now asks devnull for five replies at a time, everywhere: the commit
page, threads opened in a feed, and a deleted reply's replies. "Show more"
loads the next five. A deleted reply's replies get their own "Show more",
since a deleted commit has no page to send you to.

A refresh used to drop the pages you'd loaded once there were none left to
load. With five a page that would happen all the time, so pages loaded after
the first now stay.

A reply's page now shows the commit it replies to above it. Only the ones
before that fold behind "N earlier commits". A part of a series shows the
part before it the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@simonhamp
simonhamp marked this pull request as ready for review October 26, 2026 15:57
@simonhamp
simonhamp merged commit 075292d into main Oct 26, 2026
3 of 4 checks passed
@simonhamp
simonhamp deleted the feat/open-replies branch October 26, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant