New ReasonReact release!

chenglou · 2018-04-26 02:53:40 UTC

reasonml/reason-react/blob/master/HISTORY.md#040

# 0.4.0

**Requires** bs-platform `>=3.0.0`. Migration script is [here](https://github.com/chenglou/upgrade-reason-react).

## Breaking Changes
- Remove `SilentUpdate` and `SilentUpdateWithSideEffects`. These aren't used for a long time now.
- `didMount` now returns `unit`, per our previous warnings in the docs. To trigger a state update, use `self.send(MyAction)`.
- Remove `self.reduce` for real; use `self.send` (not to be confused with `reducer`, which is still around).
- Remove `ReasonReact.Callback` module (undocumented and unused).

## Deprecations
- `ReasonReact.stringToElement`, `arrayToElement` and `nullElement` are now **deprecated** in favor of `ReasonReact.string`, `array` and `null`!
- **Old `subscriptions` API is deprecated**. Please use the new `self.onUnmount`.
- `willReceiveProps` deprecated. We'll transition to React 16 very soon and release our binding to `deriveStateFromProps`.

## Improvements
- Use `bool` instead of `Js.boolean` (thanks to BuckleScript 3.0.0).
- Fix Router incompatibility with IE11 (#201).
- Much more streamlined internals.
- Prepare to transition to React 16.

This file has been truncated. show original

Notable changes: stringToElement is now string, no more Js.boolean warnings and internal preparations for transitioning to React 16!

aria · 2018-04-26 13:44:55 UTC

Quick question. I’ve never used ReasonReact, but I was just looking through the docs and I’m curious how you handle global state? I know that there’s no need for redux really, but currently given that there’s no context mechanism, do you just pass props everywhere?

chenglou · 2018-04-26 21:11:10 UTC

Yes (20 charsssssss)

shinzui · 2018-04-27 01:00:57 UTC

How far is the React 16 release? Is there any plan to keep ReasonReact in sync with React after that?

chenglou · 2018-05-06 06:18:25 UTC

Next release will support 16