FriendsOfFlarum / FriendsOfFlarum/split
After a split, the source discussion is shown as read even when there are new posts
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 12
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Bug Report
Current Behavior
When the split function is used to move posts to another discussion, then the source discussion is shown as read even when there are new posts in it.
Steps to Reproduce
- Split a few posts from a discussion
- Make a new post in the original discussion with a different user
- With the original user that split the discussion, open the discussion list.
- The discussion is bumped on top, however it appears as read (no bold title)
Expected Behavior
The discussion should be marked as unread if there are new posts
Additional Context
According to the user matteocontrini who first reported the issue on Discuss, the issue will resolve itself once the number of new posts exceeds the number of moved posts. Also, he said the issue is observable only by the user who performed the split, I cannot confirm this, hasn't tested with many different users.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the split flow described in the issue, then inspect how the source discussion is marked in the discussion list after posts are moved. Verify the behavior with a new post from another user; done means the source discussion is shown as unread immediately after the split.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100