prosemirror-transform - npm Package Versions

1.0.2 (2018-01-24)

Bug fixes

Fixes a crash in replace.

1.0.1 (2017-11-10)

Bug fixes

The errors raised by Transform.step now properly inherit from Error.

1.0.0 (2017-10-13)

Bug fixes

When setBlockType comes across a textblock that can't be changed due to schema constraints, it skips it instead of failing.

canSplit now returns false when the requested split goes through isolating nodes.

0.24.0 (2017-09-25)

Breaking changes

The setNodeType method on transforms is now more descriptively called setNodeMarkup. The old name will continue to work with a warning until the next release.

0.23.0 (2017-09-13)

Breaking changes

Step.toJSON no longer has a default implementation.

Steps no longer have an offset method. Map them through a map created with StepMap.offset instead.

The clearMarkup method on Transform is no longer supported (you probably needed clearIncompatible anyway).

Bug fixes

Pasting a list item at the start of a non-empty textblock now wraps the textblock in a list.

Marks on open nodes at the left of a slice are no longer dropped by Transform.replace.

New features

StepMap now has a static method offset, which can be used to create a map that offsets all positions by a given distance.

Transform objects now have a clearIncompatible method that can help make sure a node's content matches another node type.

0.22.2 (2017-07-06)

Bug fixes

Fix another bug in the way canSplit interpreted its typesAfter argument.

0.22.1 (2017-07-03)

Bug fixes

Fix crash in canSplit when an array containing null fields is passed as fourth argument.

0.22.0 (2017-06-29)

Bug fixes

canSplit now returns false when given custom after-split node types that don't match the content at that point.

Fixes canLift incorrectly returning null when lifting into an isolating node.

0.21.1 (2017-05-16)

Bug fixes

addMark no longer assumes marks always exclude only themselves.

replaceRange](https://prosemirror.net/docs/ref/version/0.21.0.html#transform.Transform.replaceRange) and deleteRange will no longer expand the range across isolating node boundaries.