guardian/scribe

Improve undo history items

Open

#98 opened on Apr 9, 2014

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (3,516 stars) (265 forks)batch import
enhancementhelp wanted

Description

It would be nice if we could set the debounce on inputs so undo/redo don't trigger for every key.

Could be an option:

Scribe(el, { debounce: 50 });

Or the ability to monkeypatch the input event would be great too.

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptScribe APIdebounce concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the Scribe initialization code to see where options are currently handled. Look at the undo/redo history implementation, likely in a file like 'scribe.js' or 'history.js'. Determine if adding a debounce option is feasible and where to integrate it. Also consider the alternative of allowing monkeypatching of the input event. The issue has 7 comments; review them for additional context.