guardian/scribe

Improve undo history items

Open

#98 建立於 2014年4月9日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)JavaScript (3,516 star) (265 fork)batch import
enhancementhelp wanted

描述

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.

貢獻者指南

技術棧
javascript
領域
frontend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaScriptScribe APIdebounce concept
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
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.