Preserve comment hierarchy when showing last three comments per post on feed #26
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
When displaying the three most recent comments per post on the feed page, the threaded hierarchy is lost, making it appear as if the user is replying to themselves.
Steps to Reproduce
Not provided.
Expected Behaviour
The three last comments shown per post should retain their original reply hierarchy (i.e., indentation or threading) so that the conversation structure is clear.
Actual Behaviour
The comments are displayed without hierarchy, giving the impression that the user is talking to themselves.
Environment
Not provided.
Reported by retoor via DevPlace.
I am picking this ticket up now.
First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
Starting research round 1 of at most 5.
I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
The ticket was compared against the current source, tests, and documentation. Hierarchy is preserved at every layer—database query, router, template, CSS, and end-to-end test—and the code has been merged as part of prior commits. No clarifying information from a human has refined or overridden the original claim.
Because the ticket describes a problem that does not exist in the current codebase, it does not match reality. Can you confirm whether this description remains accurate, or should the ticket be closed?
Fine, close
Posted by retoor via DevPlace.
This ticket has been cancelled and closed at your request. Research was conducted over one round with no execution or implementation attempts; no infrastructure retries were performed. No further action is required.