Changelog History
Page 10
-
v0.13.0 Changes
August 15, 2016BREAKING
The
renderNode
andrenderMark
properties are gone! Previously, rendering nodes and marks happened via these two properties of the<Editor>
, but this has been replaced by the newschema
property. Check out the updated examples to see how to define a schema! There's a good chance this eliminates extra code for most use cases! :smile:The
renderDecorations
property is gone! Decoration rendering has also been replaced by the newschema
property of the<Editor>
.
-
v0.12.0 Changes
August 09, 2016BREAKING
The
data.files
property is now anArray
. Previously it was a nativeFileList
object, but needed to be changed to add full support for pasting an dropping files in all browsers. This shouldn't affect you unless you were specifically depending on it being array-like instead of a trueArray
.
-
v0.11.0 Changes
August 04, 2016BREAKING
Void nodes are renderered implicitly again! Previously Slate had required that you wrap void node renderers yourself with the exposed
<Void>
wrapping component. This was to allow for selection styling, but a change was made to make selection styling able to handled in JavaScript. Now the<Void>
wrapper will be implicitly rendered by Slate, so you do not need to worry about it, and "voidness" only needs to toggled in one place, theisVoid: true
property of a node.
-
v0.10.0 Changes
July 29, 2016BREAKING
Marks are now renderable as components. Previously the only supported way to render marks was by returning a
style
object. Now you can return a style object, a class name string, or a full React component. Because of this, the DOM will be renderered slightly differently than before, resulting in an extra<span>
when rendering non-component marks. This won't affect you unless you were depending on the DOM output by Slate for some reason.
-
v0.9.0 Changes
July 28, 2016BREAKING
The
wrap
andunwrap
method signatures have changed! Previously, you would passtype
anddata
as separate parameters, for example:wrapBlock('code', { src: true })
. This was inconsistent with other transforms, and has been updated such that a single argument ofproperties
is passed instead. So that example could now be:wrapBlock({ type: 'code', { data: { src: true }})
. You can still pass atype
string as shorthand, which will be the most frequent use case, for example:wrapBlock('code')
.
-
v0.8.13
April 25, 2020 -
v0.8.12
April 25, 2020 -
v0.8.11
November 10, 2019 -
v0.8.10
August 27, 2019 -
v0.8.9
August 22, 2019