OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2026-01-15 12:15:22 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Add context deprecation to changelog, reformat

Browse Source
This commit is contained in:
Paul O’Shannessy
2014-02-20 10:31:46 -08:00
parent c32e398a5c
commit f3c1383af9
3 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGELOG.md
View File

@@ -12,6 +12,7 @@
- On mouse wheel events, `deltaY` is no longer negated
- 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)
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
- `this.context` on components is now reserved for internal use by React
#### New Features

2
docs/_posts/2014-02-16-react-v0.9-rc1.md
View File

@@ -68,7 +68,7 @@ In cases where you want to preserve the space adjacent to a newline, you can wri
- On mouse wheel events, `deltaY` is no longer negated
- 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)
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
- this.context on components is now reserved for internal use by React
- `this.context` on components is now reserved for internal use by React
#### New Features

2
docs/_posts/2014-02-20-react-v0.9.md
View File

@@ -76,7 +76,7 @@ In cases where you want to preserve the space adjacent to a newline, you can wri
- On mouse wheel events, `deltaY` is no longer negated
- 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)
- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead
- this.context on components is now reserved for internal use by React
- `this.context` on components is now reserved for internal use by React
#### New Features