Skip to content

Commit b72f8b6

Browse files
committed
apologize in the upgrade guide
1 parent dde1701 commit b72f8b6

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

UPGRADE_GUIDE.md

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,29 @@ To see discussion around these API changes, please refer to the
55
[changelog](/CHANGELOG.md) and visit the commits and issues they
66
reference.
77

8-
0.12.x -> 0.13.x
8+
0.13.2 -> 0.13.3
99
----------------
1010

11+
Like many others in the community, we misunderstood the "mixins are
12+
going away" sentiment. Mixins, along with `React.createClass` are not
13+
going away any time soon, and definitely not until ES6 classes have
14+
better answers to replace what mixins do (like decorators).
15+
16+
So, don't access context, use the mixins, sorry for the churn, we know
17+
it can be frustrating.
18+
19+
Upgrade path from `0.13.2` to `0.13.3` is to put your code back to how
20+
it was in `0.12.x`. The context stuff will still work, so you can do it
21+
incrementally.
22+
23+
0.12.x -> 0.13.2 (PLEASE SKIP THIS)
24+
-----------------------------------
25+
26+
**SKIP THIS UPGRADE AND GO STRAIGHT TO 0.13.3**
27+
28+
`0.13.3` has the same API as `0.12.x`, so please upgrade to `0.13.3` and
29+
skip the `0.13.0-0.13.2` stuff and leave your code alone :)
30+
1131
React introduced the ability to use ES6 classes for component
1232
definitions, which has the side-effect of mixins not being "the thing"
1333
anymore. Our mixins like `State` and `Navigation` just proxied calls to

0 commit comments

Comments
 (0)