{"commit":{"authorName":"Paul O’Shannessy","authorEmail":"paul@oshannessy.com","subject":"0.11-rc blog post","revision":"b8cc3f510a61b6d89c21a9a0cac969346f28724c","authoredAt":"2014-07-13T12:54:41-07:00","shortRevision":"b8cc3f510a"},"body":"","parents":["ab690586d391c48a8c9561ff64aa97ecf8e28af5"],"files":[{"path":"docs\/_posts\/2014-07-13-react-v0.11-rc1.md","status":"A"},{"path":"docs\/downloads\/react-0.11.0-rc1.zip","status":"A"}],"patch":"diff --git a\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md b\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md\nnew file mode 100644\nindex 0000000000..091f6c6b59\n--- \/dev\/null\n+++ b\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md\n@@ -0,0 +1,147 @@\n+---\n+title: React v0.11 RC\n+layout: post\n+author: Paul O’Shannessy\n+---\n+\n+It's that time again… we're just about ready to ship a new React release! v0.11 includes a wide array of bug fixes and features. We highlighted some of the most important changes below, along with the full changelog.\n+\n+The release candidate is available for download from the CDN:\n+\n+* **React** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **React with Add-Ons** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **In-Browser JSX transformer** \n+ \n+\n+We've also published version `0.11.0-rc1` of the `react` and `react-tools` packages on npm and the `react` package on bower.\n+\n+Please try these builds out and [file an issue on GitHub](https:\/\/github.com\/facebook\/react\/issues\/new) if you see anything awry.\n+\n+\n+# Blog Post\n+\n+## `getDefaultProps`\n+\n+Starting in React 0.11, `getDefaultProps()` is called only once when `React.createClass()` is called, instead of each time a component is rendered. This means that `getDefaultProps()` can no longer vary its return value based on `this.props` and any objects will be shared across all instances. This change improves performance and will make it possible in the future to do PropTypes checks earlier in the rendering process, allowing us to give better error messages.\n+\n+\n+## Rendering to `null`\n+\n+Since React's release, people have been using work arounds to \"render nothing\". Usually this means returning an empty `` or ``. Some people even got clever and started returning `` to avoid extraneous DOM nodes. We finally provided a \"blessed\" solution that allows developers to writing meaningful code. Returning `null` in an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `

dillon1000/react

Files changed