QuantumBadger / QuantumBadger/RedReader
[Bug] After editing, the comment is not refreshed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
After editing a comment (or post), on save, the user is returned to the prior-to-editing cached copy.
If the comment (or post) is then again edited, the user is presented with the prior-to-editing cached copy. The second edit then overwrites the first.
This hus o typo! // original copy
This has o typo! // first edit
This hus o typo! // after save, cached copy displayed
This hus a typo! // second edit is to cached copy, first edit is overwritten
I see the value in caching, but stale caches lead to inconsistencies.
Contributor guide
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 comment and post edit flow described in the issue, then trace how the saved content is loaded and cached after submission. Done means the edited content is displayed immediately after saving and a second edit preserves the first edit rather than overwriting it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100