introvertuous / redux-undone Goto Github PK

The way that I usually handle clusters of the same action that all need to be undone with a single undo action, is to create an additional action that is not undoable and perform the undoable action first and subsequent calls using the non undoable variant, so you get a proper undo to the initiating action. This method is super tedious and requires lots of boilerplate.

A better way would be to have an interval, and compare the time between actions of a particular type. So, if an action is dispatched, we push a historical entry, and then the same action is dispatched less than 100ms later, we do not add a historical entry for that action.

ideally history data would be stored in the redux store that the client is building, which would make for a clean api.

once complete, make sure to fix the example:
132737a#diff-fd9c790e80143e73075639ef6d05317c

• convert example to typescript
• make sure you are getting proper types from base lib

• node
• browser

When you use a thunk for a transformation, and dispatch more than one action we run in a bit of an issue. If these actions are both undo-able then we are creating more future entries than we are removing from the past, which does not feel correct.

the ordering probably should have been: (action, prevState, nextState)