changelogs.md


prosemirror/prosemirror-history

Repository  -  API  -  Source

1.0.3

October 8, 2018

Bug fixes

Appending a transaction to an undo transaction will no longer immediately clear the redo history.

When handling appended transactions, the history will keep the last step in the original transaction, not the one from the appended transaction, for testing whether a subsequent transaction is adjacent to the previous one.

1.0.2

March 13, 2018

Bug fixes

Fix a bug that could corrupt the history when rebasing changes because of collaborative editing.

1.0.1

March 5, 2018

Bug fixes

Fix crash that could occur (in specific circumstance) when redoing.

0.24.0

September 25, 2017

New features

It is no longer necessary to manually enable the preserveItems option to the history plugin when using collaborative editing. (This behavior is now automatically enabled when necessary.)

0.20.0

April 3, 2017

Bug fixes

Appended transactions no longer generate undo history events.

0.19.0

March 16, 2017

New features

A new function closeHistory can be used to force separation of history events at the start of a given transaction.

0.18.0

February 24, 2017

Bug fixes

Fix a problem where simultaneous collaborative editing could break the undo history.

0.17.1

February 2, 2017

Bug fixes

Fix issue where collaborative editing corner cases could corrupt the history.

0.12.1

November 1, 2016

Bug fixes

Fix crash in undo or redo commands when the history is empty.

0.12.0

October 21, 2016

Breaking changes

The history export is now a function that creates a history plugin, rather than a plugin instance.

New features

Add a newGroupDelay plugin option. This brings back the behavior where pausing between edits will automatically cause the history to put subsequent changes in a new undo event.

0.11.0

September 21, 2016

Breaking changes

Moved into a separate module. Now acts as a plugin that can be omitted or replaced by a different implementation if desired.

Merging subsequent changes into a single undo 'event' is now done by proximity in the document (the changes must touch) rather than in time. This will probably have to be further refined.