No undo/redo for image-level operations (crop, replace)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Bug: Missing undo/redo for image operations
Crop and replace operations on image annotations bypass the undo stack, making them irreversible. Users can lose work if they accidentally crop or replace an image.
Current behavior: annotationHistory undo stack is not updated for image-level mutations (crop, replace).
Expected: All image-level operations should push to the undo stack.
Category: bug | Severity: medium
🤖 Found by Hermes Autonomous Orchestrator
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 tracing the annotationHistory undo stack and the entry points for crop and replace operations. Verify how other image mutations record history, then make sure both operations are undoable and redoable without losing the annotation state. Confirm the behavior manually in the browser or with any existing history tests.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100