usePacedMutations value regression while persisting
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.9k
- Forks
- 266
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 55
Description
- I've validated the bug against the latest version of DB packages
Describe the bug
(I tested this using only electric)
It seems there is a regression (to the latest value before any optimistic update) in collection's data using paced mutations while persisting (that also causes a re-render, that seems an ui glitch).
It seems similar to #904, but the behavior is somehow different.
To Reproduce
https://github.com/fcannizzaro/tanstack-db-previous-value/
Expected behavior
It should keep the latest value while persisting (like the non paced mutation)
Screenshots
| UI | Logs |
|---|---|
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 with the linked tanstack-db-previous-value reproduction and compare paced mutations with non-paced mutations during persistence. Trace the collection update and rendering entry points involved in that reproduction; done means the latest value remains visible while the mutation is persisting, without the reported regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100