{"parents":["9125f68194cf99e55e027b6cc7ed34325c9855e4"],"commit":{"authoredAt":"2014-02-12T20:45:17-08:00","subject":"Blog post for 0.9 release candidate","authorName":"Ben Alpert","revision":"9e160df86806c2746735492263401aac725281af","shortRevision":"9e160df868","authorEmail":"spicyjalapeno@gmail.com"},"files":[{"path":"docs\/_posts\/2014-02-16-react-v0.9-rc1.md","status":"A"},{"path":"docs\/downloads\/react-0.9.0-rc1.zip","status":"A"}],"body":"","patch":"diff --git a\/docs\/_posts\/2014-02-16-react-v0.9-rc1.md b\/docs\/_posts\/2014-02-16-react-v0.9-rc1.md\nnew file mode 100644\nindex 0000000000..960b26c65e\n--- \/dev\/null\n+++ b\/docs\/_posts\/2014-02-16-react-v0.9-rc1.md\n@@ -0,0 +1,132 @@\n+---\n+title: React v0.9 RC\n+layout: post\n+author: Ben Alpert\n+---\n+\n+We're almost ready to release React v0.9! We're posting a release candidate so that you can test your apps on it; we'd much prefer to find show-stopping bugs now rather than after we release.\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.9.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+## Upgrade Notes\n+\n+In addition to the changes to React core listed below, we've made a small change to the way JSX interprets whitespace to make things more consistent. With this release, space between two components on the same line will be preserved, while a newline separating a text node from a tag will be eliminated in the output. Consider the code:\n+\n+```html\n+

\n+ Monkeys:\n+ {listOfMonkeys} {submitButton}\n+<\/div>\n+```\n+\n+In v0.8 and below, it was transformed to the following:\n+\n+```javascript\n+React.DOM.div(null,\n+ \" Monkeys: \",\n+ listOfMonkeys, submitButton\n+)\n+```\n+\n+In v0.9, it will be transformed to this JS instead:\n+\n+```javascript{2,3}\n+React.DOM.div(null,\n+ \"Monkeys:\",\n+ listOfMonkeys, \" \", submitButton\n+)\n+```\n+\n+We believe this new behavior is more helpful and elimates cases where unwanted whitespace was previously added.\n+\n+In cases where you want to preserve the space adjacent to a newline, you can write a JS string like `{\"Monkeys: \"}` in your JSX source. We've included a script to do an automated codemod of your JSX source tree that preserves the old whitespace behavior by adding and removing spaces appropriately. You can [install jsx\\_whitespace\\_transformer from npm](https:\/\/github.com\/facebook\/react\/blob\/master\/npm-jsx_whitespace_transformer\/README.md) and run it over your source tree to modify files in place. The transformed JSX files will preserve your code's existing whitespace behavior.\n+\n+## Changelog\n+\n+### React Core\n+\n+#### Breaking Changes\n+\n+- The lifecycle methods `componentDidMount` and `componentDidUpdate` no longer receive the root node as a parameter; use `this.getDOMNode()` instead\n+- Whenever a prop is equal to `undefined`, the default value returned by `getDefaultProps` will now be used instead\n+- `React.unmountAndReleaseReactRootNode` was previously deprecated and has now been removed\n+- `React.renderComponentToString` is now synchronous and returns the generated HTML string\n+- Full-page rendering (that is, rendering the `` tag using React) is now supported only when starting with server-rendered markup\n+- On mouse wheel events, `deltaY` is no longer negated\n+- When prop types validation fails, a warning is logged instead of an error thrown (with the production build of React, the type checks are now skipped for performance)\n+- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead\n+\n+#### New Features\n+\n+- React now never rethrows errors, so stack traces are more accurate and Chrome's purple break-on-error stop sign now works properly\n+- Added a new tool for profiling React components and identifying places where defining `shouldComponentUpdate` can give performance improvements\n+- Added support for SVG tags `defs`, `linearGradient`, `polygon`, `radialGradient`, `stop`\n+- Added support for more attributes:\n+ - `noValidate` and `formNoValidate` for forms\n+ - `property` for Open Graph `` tags\n+ - `sandbox`, `seamless`, and `srcDoc` for `

dillon1000/react

Files changed