From 30c7c808ab3432694c2e6751d6e37c1bcde269c9 Mon Sep 17 00:00:00 2001 From: SunHuawei Date: Tue, 24 Jan 2017 00:43:48 +0800 Subject: [PATCH] Fix a typo (#8580) --- _posts/2016-07-13-mixins-considered-harmful.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2016-07-13-mixins-considered-harmful.md b/_posts/2016-07-13-mixins-considered-harmful.md index 6d72758c..ad965926 100644 --- a/_posts/2016-07-13-mixins-considered-harmful.md +++ b/_posts/2016-07-13-mixins-considered-harmful.md @@ -440,7 +440,7 @@ Multiple components may be sharing `RowMixin` to render the header, and each of If you see rendering logic inside a mixin, it’s time to extract a component! -Instead of `RowMixin`, we will define a `` component. We will also replace the convention of defining a `getHeaderText()` method with the standard mechanism of top-data flow in React: passing props. +Instead of `RowMixin`, we will define a `` component. We will also replace the convention of defining a `getHeaderText()` method with the standard mechanism of top-data flow in React: passing props. Finally, since neither of those components currently need lifecycle hooks or state, we can declare them as simple functions: