		Like HISTORY.md, but for planned future versions and subject to change. The vocabulary here uses the past tense, to pretend that the versions are already published.

		# 0.2.0
		# Far into the future

		Breaking update (sorry!)
		- Static tree (prevents top-level component switching, enables destructuring of owned tree).
		- Getting rid of keys altogether in the common case.
		- Getting rid of ref.
		- Making a great list abstraction to model dynamically changing lists/scrollers.

		We've finally removed `ReactRe`. It's been deprecated since 0.1.4. And we've offered a comprehensive migration path below.
		# 0.2.1

		- Instead of `fun state self => ...`, we've now rolled `state` into `self`, and now, you have `fun {state, self} => ...`. Feel free to destructure and get whatever you need!
		- This also means we don't need `ReasonReact.statelessComponent` anymore. The reasoning for adding it was just to avoid some confusing type errors when people use `statelessComponent` in conjunction with `fun state self => ...` rather than `fun () self => ...`.
		- `enqueue`. Best thing ever.
		- Secret (feature-that-must-not-be-named)
		- `self` now contains a new prop, `retainedProps`. This is a new feature that solves the previous slightly inconvenient way of forwarding props to state, as described in the old API's lifecycle methods. Now there's a dedicated API for it! The docs describes this in detail.
		- `enqueue`. Best thing ever.
		- remove create-react-class
		- Set lifecycles to null when they do nothing. React skips over lifecycles that are set to null, we currently have wrappers around all of them, so things like didMount are enqueued for every component.
		- `ReactDOMRe.createElement` (usually used through the JSX `<div> foo </div>`) has a new implementation that fixes an inadvertent children key warning in the previous version.
		- either rename `willReceiveProps` to `propsReceived`, or keep the same name and make it take oldNew self bag

HISTORY.md

		@@ -0,4 +1,15 @@
		# 0.2.0

		Breaking update (sorry!)

		We've finally removed `ReactRe`. It's been deprecated since 0.1.4. And we've offered a comprehensive migration in the 0.1.4 section below.

		We've given folks a bit of breathing room in terms of breaking changes; now we're shipping another one, this time with a small migration script. After installing reason-react, use `node node_modules/reason-react/migrateFrom015To020.js myReasonFile.re`

		- Instead of `fun state self => ...`, we've now rolled `state` into `self`, and now, you have `fun {state, self} => ...`. Feel free to destructure and get whatever you need!
		- `self` now contains a new prop, `retainedProps`. This is a new (non-breaking) feature that solves the previous slightly inconvenient way of forwarding props to state, as described in the old API's lifecycle methods. Now there's a dedicated API for it! The docs describes this in detail.

		# 0.1.5

		Non-breaking update. Works better with bs-platform >=1.8.0 (currently unreleased), which comes with the following ReasonReact JSX fixes:
		Non-breaking update. Works better with bs-platform >=1.8.0, which comes with the following ReasonReact JSX fixes:

		@@ -5,0 +16,0 @@ - JSX ppx now recursively transforms component's props.

package.json

		{
		"name": "reason-react",
		"version": "0.1.5",
		"version": "0.2.0",
		"description": "",
		@@ -5,0 +5,0 @@ "main": "index.js",

src/reactRe.re

src/reactRe.rei

docs/blog.html