From 1a69d7c19df6f462fc9b3ed4a9e15fc1aacca6e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Tue, 3 Mar 2015 12:47:12 -0800 Subject: [PATCH] Facebook, not FaceBook --- _posts/2015-03-03-react-v0.13-rc2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2015-03-03-react-v0.13-rc2.md b/_posts/2015-03-03-react-v0.13-rc2.md index 53bc780b..dffe4648 100644 --- a/_posts/2015-03-03-react-v0.13-rc2.md +++ b/_posts/2015-03-03-react-v0.13-rc2.md @@ -53,6 +53,6 @@ var newChildren = React.Children.map(this.props.children, function(child) { > Note: `React.cloneElement(child, { ref: 'newRef' })` *DOES* override the `ref` so it is still not possible for two parents to have a ref to the same child, unless you use callback-refs. -This was a critical feature to get into React 0.13 since props are now immutable. The upgrade path is often to clone the element, but by doing so you might lose the `ref`. Therefore, we needed a nicer upgrade path here. As we were upgrading callsites at FaceBook we realized that we needed this method. We got the same feedback from the community. Therefore we decided to make another RC before the final release to make sure we get this in. +This was a critical feature to get into React 0.13 since props are now immutable. The upgrade path is often to clone the element, but by doing so you might lose the `ref`. Therefore, we needed a nicer upgrade path here. As we were upgrading callsites at Facebook we realized that we needed this method. We got the same feedback from the community. Therefore we decided to make another RC before the final release to make sure we get this in. We plan to eventually deprecate `React.addons.cloneWithProps`. We're not doing it yet, but this is a good opportunity to start thinking about your own uses and consider using `React.cloneElement` instead. We'll be sure to ship a release with deprecation notices before we actually remove it so no immediate action is necessary.