How to save a snapshot of a specific version？
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
I have the following usage scenarios：
- When a user edits, save the current version
- He can see the data of this version.
I want to know if the amount of data in the op operation is large, how can it be implemented better, such as how to save a specific version of Milestone Snapshots
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
No file, test, or entry point is named. Start by tracing how ShareDB stores and retrieves operation history and versions, then compare that behavior with the two snapshot scenarios described. Done would be a documented, agreed approach for saving and reading specific-version snapshots, including how large operation histories should be handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100