Add context deprecation to changelog, reformat
Paul O’Shannessy committed
Feb 20, 2014 at 10:31 UTC
f3c1383af9e8abaf301df246c8c57b37a702c9aa
3 files changed
+3
-2
CHANGELOG.md
+1
@@ -12,6 +12,7 @@
12
- On mouse wheel events, `deltaY` is no longer negated
13
- When prop types validation fails, a warning is logged instead of an error thrown (with the production build of React, type checks are now skipped for performance)
14
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
15
+- `this.context` on components is now reserved for internal use by React
16
17
#### New Features
18
docs/_posts/2014-02-16-react-v0.9-rc1.md
+1
-1
@@ -68,7 +68,7 @@ In cases where you want to preserve the space adjacent to a newline, you can wri
68
- On mouse wheel events, `deltaY` is no longer negated
69
- 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)
70
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
71
-- this.context on components is now reserved for internal use by React
71
+- `this.context` on components is now reserved for internal use by React
72
73
#### New Features
74
docs/_posts/2014-02-20-react-v0.9.md
+1
-1
@@ -76,7 +76,7 @@ In cases where you want to preserve the space adjacent to a newline, you can wri
76
- On mouse wheel events, `deltaY` is no longer negated
77
- When prop types validation fails, a warning is logged instead of an error thrown (with the production build of React, type checks are now skipped for performance)
78
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
79
-- this.context on components is now reserved for internal use by React
79
+- `this.context` on components is now reserved for internal use by React
80
81
#### New Features
82