From dba7b650f96d4caed17fd3a561ab187e1d9741c0 Mon Sep 17 00:00:00 2001 From: Clement Hoang Date: Tue, 28 Nov 2017 13:08:31 -0800 Subject: [PATCH] Update changelog --- ...7-11-28-react-v16.2.0-fragment-support.md} | 26 ++++++++++++------- 1 file changed, 17 insertions(+), 9 deletions(-) rename content/blog/{2017-11-28-fragments-in-react-v16.2.md => 2017-11-28-react-v16.2.0-fragment-support.md} (89%) diff --git a/content/blog/2017-11-28-fragments-in-react-v16.2.md b/content/blog/2017-11-28-react-v16.2.0-fragment-support.md similarity index 89% rename from content/blog/2017-11-28-fragments-in-react-v16.2.md rename to content/blog/2017-11-28-react-v16.2.0-fragment-support.md index 230b2278..a0740519 100644 --- a/content/blog/2017-11-28-fragments-in-react-v16.2.md +++ b/content/blog/2017-11-28-react-v16.2.0-fragment-support.md @@ -1,5 +1,5 @@ --- -title: "Fragments in React v16.2" +title: "React v16.2.0: Fragment Support" author: [clemmy] --- @@ -124,7 +124,7 @@ Fragment syntax in JSX was inspired by prior art such as the `XMLList() <>` c ### Keyed Fragments -Note that the `<>` syntax does not accept attributes, including keys. +Note that the `<>` syntax does not accept attributes, including keys. If you need a keyed fragment, you can use `` directly. An use case for this is mapping a collection to an array of fragments -- for example, to create a description list: @@ -287,19 +287,27 @@ Refer to the documentation for [detailed installation instructions](/docs/instal ## Changelog -#### React +### React -* Add Fragment as a named export to React. ([@clemmy](https://github.com/clemmy) in [#10783](https://github.com/facebook/react/pull/10783)) +* Add `Fragment` as named export to React. ([@clemmy](https://github.com/clemmy) in [#10783](https://github.com/facebook/react/pull/10783)) +* Support experimental Call/Return types in `React.Children` utilities. ([@MatteoVH](https://github.com/MatteoVH) in [#11422](https://github.com/facebook/react/pull/11422)) -#### React DOM +### React DOM -* Fix regression where radio button onChange events are not fired as expected. ([@landvibe](https://github.com/landvibe) in [#11227](https://github.com/facebook/react/pull/11227)) +* Fix radio buttons not getting checked when using multiple lists of radios. ([@landvibe](https://github.com/landvibe) in [#11227](https://github.com/facebook/react/pull/11227)) +* Fix radio buttons not receiving the `onChange` event in some cases. ([@jquense](https://github.com/jquense) in [#11028](https://github.com/facebook/react/pull/11028)) -* Fix incorrectly checked radio buttons when using multiple lists of radio buttons. ([@darth-cheney](https://github.com/darth-cheney) in [#10739](https://github.com/facebook/react/pull/10739)) +### React Test Renderer -#### React Test Renderer +* Fix `setState()` callback firing too early when called from `componentWillMount`. ([@accordeiro](https://github.com/accordeiro) in [#11507](https://github.com/facebook/react/pull/11507)) -* Fix setState callback getting called before component state is updated ([@accordeiro](https://github.com/accordeiro) in [#11507](https://github.com/facebook/react/pull/11507)) +### React Reconciler + +* Expose `react-reconciler/reflection` with utilities useful to custom renderers. ([@rivenhk](https://github.com/rivenhk) in [#11683](https://github.com/facebook/react/pull/11683)) + +### Internal Changes + +* Many tests were rewritten against the public API. Big thanks to [everyone who contributed](https://github.com/facebook/react/issues/11299)! ## Acknowledgments