2.1 KiB
Changelog
This document maintains a list of changes to the slate-html-serializer
package with each new version. Until 1.0.0
is released, breaking changes will be added as minor version bumps, and smaller changes won't be accounted for since the library is moving quickly.
0.6.0
— March 22, 2018
BREAKING
- Returning
null
now ignores the node. Previously it would be treated the same asundefined
, which will move on to the next rule in the stack. Now it ignores the node and moves onto the next node instead.
0.5.0
— January 4, 2018
BREAKING
-
The
kind
property of Slate objects has been renamed toobject
. This is to reduce the confusion over the difference between "kind" and "type" which are practically synonyms. The "object" name was chosen to match the Stripe API, since it seems like a sensible choice and reads much more nicely when looking through JSON. -
Serializing with
parse5
is no longer possible. The codebase previously made concessions to allow this, but it was never a good idea becauseparse5
does not match theDOMParser
behavior exactly. Instead, you should usejsdom
to get a matching behavior, otherwise your serialization rules need to account for two slightly different syntax trees.
0.4.0
— October 27, 2017
BREAKING
- Remove all previously deprecated code paths. This helps to reduce some of the complexity in Slate by not having to handle these code paths anymore. And it helps to reduce file size. When upgrading, it's highly recommended that you upgrade to the previous version first and ensure there are no deprecation warnings being logged, then upgrade to this version.
0.3.0
— October 27, 2017
BREAKING
- Updated to work with
slate@0.29.0
. This is required becauseslate-html-serializer
needs access to the newValue
model.
0.2.0
— October 14, 2017
BREAKING
- Updated work with
slate@0.27.0
. The new version of Slate renames the oldRange
model toLeaf
, and the oldSelection
model toRange
.
0.1.0
— September 17, 2017
🎉