From c4726becd97ff0c78acc67d6f4389d6275ec02d8 Mon Sep 17 00:00:00 2001 From: Marcel Weiher Date: Wed, 2 Jan 2019 15:48:15 +0100 Subject: [PATCH] Update Readme: remove "pure" from pure function MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://www.reddit.com/r/reactjs/comments/abj7hn/uis_are_not_pure_functions_of_the_model_reactjs/ed1h20x/ "To elaborate a bit, React components aren’t always “pure” in strict FP sense of the word. They’re also not always functions (although we’re adding a stateful function API as a preferred alternative to classes soon). Support for local state and side effects is absolutely a core feature of React components and not something we avoid for “purity" --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 91d46fd..0633f0b 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ I like to have a simpler mental model that I can ground myself in. ## Transformation -The core premise for React is that UIs are simply a projection of data into a different form of data. The same input gives the same output. A simple pure function. +The core premise for React is that UIs are simply a projection of data into a different form of data. The same input gives the same output. A simple function. ```js function NameBox(name) {