Skip to content

Impl ReplyTree data layer#1044

Open
joelmuraguri wants to merge 6 commits intojoel/expose-post-thread-parent-urifrom
joel/reply-tree-data-layer
Open

Impl ReplyTree data layer#1044
joelmuraguri wants to merge 6 commits intojoel/expose-post-thread-parent-urifrom
joel/reply-tree-data-layer

Conversation

@joelmuraguri
Copy link
Collaborator

No description provided.

@joelmuraguri joelmuraguri requested a review from tunjid February 25, 2026 12:33
@joelmuraguri joelmuraguri changed the base branch from main to joel/expose-post-thread-parent-uri February 25, 2026 12:34
@gemini-code-assist
Copy link

Summary of Changes

Hello @joelmuraguri, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a ReplyTree data structure to better represent threaded conversations in the timeline. It modifies the data layer to support the new structure, updates the database schema, and adjusts the UI to accommodate the changes. The goal is to improve the way replies are displayed and managed in the timeline.

Highlights

  • ReplyTree Data Structure: Introduces a ReplyTree data structure to represent threaded conversations, replacing the previous Thread implementation for descendant posts.
  • TimelineItem Updates: Modifies the TimelineItem sealed class to include ReplyTree as a possible item type, affecting how timeline items are filtered and displayed.
  • Database Changes: Updates the database schema to include parentPostUri in the ThreadedPostEntity, enabling the construction of the ReplyTree.
  • UI Adjustments: Adjusts the UI to accommodate the new ReplyTree structure, ensuring that post reason lines and timeline filtering work correctly.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Activity
  • Introduced ReplyTree data structure for threaded conversations.
  • Modified TimelineItem to include ReplyTree.
  • Updated database schema to include parentPostUri.
  • Adjusted UI to accommodate ReplyTree.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request implements the data layer for ReplyTree, which is a new way to represent threaded conversations. The changes introduce TimelineItem.ReplyTree and ReplyNode data classes and update the TimelineRepository to build these trees from fetched post data. The review identifies a critical bug where ReplyTree items are incorrectly filtered out from the timeline view, and a performance issue in the recursive function used to build the reply tree. Suggestions are provided to fix both issues.

) = with(context) {
val lastItem = list.lastOrNull()
when {
// To start or for the OP, start a new thread
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this method should be left alone, its trying to do two things. You should have a different method for reply building.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After switching postThreadedItems to use ::spinReplyTree, spinThread is no longer called anywhere in the codebase. I want to make sure I understand the intent here, should spinThread be removed for now and reintroduced when there is an actual call site for it or is there a planned use case coming that I should be aware of so I can keep it in place?

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.

Introduce reply tree data model and update thread processing logic

2 participants