@samitouri / QOS-React-2 / commits / 085bf8635c

Add deprecation note to blog post and changelog

Ben Alpert committed Mar 10, 2015 at 14:22 UTC 085bf8635c40e78b4650e3dc4bffc8f96d3a77a7
2 files changed +2
CHANGELOG.md
+1
@@ -4,6 +4,7 @@
4
5 #### Breaking Changes
6
7 +* Deprecated patterns that warned in 0.12 no longer work: most prominently, calling component classes without using JSX or React.createElement and using non-component functions with JSX or createElement
8 * Mutating `props` after an element is created is deprecated and will cause warnings in development mode; future versions of React will incorporate performance optimizations assuming that props aren't mutated
9 * Static methods (defined in `statics`) are no longer autobound to the component class
10 * `ref` resolution order has changed slightly such that a ref to a component is available immediately after its `componentDidMount` method is called; this change should be observable only if your component calls a parent component's callback within your `componentDidMount`, which is an anti-pattern and should be avoided regardless
docs/_posts/2015-03-10-react-v0.13.md
+1
@@ -35,6 +35,7 @@ We've also published version `0.13.0` of the `react` and `react-tools` packages
35
36 #### Breaking Changes
37
38 +* Deprecated patterns that warned in 0.12 no longer work: most prominently, calling component classes without using JSX or React.createElement and using non-component functions with JSX or createElement
39 * Mutating `props` after an element is created is deprecated and will cause warnings in development mode; future versions of React will incorporate performance optimizations assuming that props aren't mutated
40 * Static methods (defined in `statics`) are no longer autobound to the component class
41 * `ref` resolution order has changed slightly such that a ref to a component is available immediately after its `componentDidMount` method is called; this change should be observable only if your component calls a parent component's callback within your `componentDidMount`, which is an anti-pattern and should be avoided regardless