From 8bf0697a15b1ec7cc0c20e9f849d4d04fd8e58bf Mon Sep 17 00:00:00 2001 From: Ian Storm Taylor Date: Thu, 28 Jul 2016 16:38:41 -0700 Subject: [PATCH] update history --- History.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/History.md b/History.md index 99ff7ae7c..788c4f5e2 100644 --- a/History.md +++ b/History.md @@ -5,6 +5,11 @@ This document maintains a list of changes to Slate with each new version. Until --- +### `0.9.0` — _July 28, 2016_ + +- **The `wrap` and `unwrap` method signatures have changed!** Previously, you would pass `type` and `data` as separate parameters, for example: `wrapBlock('code', { src: true })`. This was inconsistent with other transforms, and has been updated such that a single argument of `properties` is passed instead. So that example could now be: `wrapBlock({ type: 'code', { data: { src: true }})`. You can still pass a `type` string as shorthand, which will be the most frequent use case, for example: `wrapBlock('code')`. + + ### `0.8.0` — _July 27, 2016_ - **The `onKeyDown` and `onBeforeInput` handlers signatures have changed!** Previously, some Slate handlers had a signature of `(e, state, editor)` and others had a signature of `(e, data, state, editor)`. Now all handlers will be passed a `data` object—which contains Slate-specific data related to the event—even if it is empty. This is helpful for future compatibility where we might need to add data to a handler that previously didn't have any, and is nicer for consistency. The `onKeyDown` handler's new `data` object contains the `key` name, `code` and a series of `is*` properties to make working with hotkeys easier. The `onBeforeInput` handler's new `data` object is empty.