From ea4dd2068d3c58572fa5265cb2ab13e7910201b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Wed, 28 Jan 2015 00:01:54 -0800 Subject: [PATCH] One more typo fix in the 0.13 beta blog post --- docs/_posts/2015-01-27-react-v0.13.0-beta-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2015-01-27-react-v0.13.0-beta-1.md b/docs/_posts/2015-01-27-react-v0.13.0-beta-1.md index 8b9bb80315..01ad9c1d30 100644 --- a/docs/_posts/2015-01-27-react-v0.13.0-beta-1.md +++ b/docs/_posts/2015-01-27-react-v0.13.0-beta-1.md @@ -115,7 +115,7 @@ class Counter extends React.Component { Unfortunately, we will not launch any mixin support for ES6 classes in React. That would defeat the purpose of only using idiomatic JavaScript concepts. -There is no standard and universal way to define mixins in JavaScript. In fact, several features to support mixins was dropped from ES6 today. There are a lot of libraries with different semantics. We think that there should be one way of defining mixins that you can use for any JavaScript class. React just making another doesn't help that effort. +There is no standard and universal way to define mixins in JavaScript. In fact, several features to support mixins were dropped from ES6 today. There are a lot of libraries with different semantics. We think that there should be one way of defining mixins that you can use for any JavaScript class. React just making another doesn't help that effort. Therefore, we will keep working with the larger JS community to create a standard for mixins. We will also start designing a new compositional API that will help make common tasks easier to do without mixins. E.g. first-class subscriptions to any kind of Flux store.