Infinite & persistent undo history
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
I'm always frustrated when my kids loose half a day of daddy support work.
Describe the solution you'd like
Make the "undo" history keeping every step, flushing only on request (in the settings).
Describe alternatives you've considered
I could copy the results of every project to a Google-Docs or my own GitHub files, but probably I will be mostly to lazy for this.
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
No file, test, or entry point is named in the issue. Start by locating the editor's undo-history implementation and settings handling, then determine how history is currently flushed. Done means undo history persists across the requested scope and can be flushed through a setting, with behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100