New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the "pure" from "pure function" #12

Open
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
1 participant
@mpw
Copy link

mpw commented Jan 2, 2019

The mapping from the state/model is not a pure function, so remove the word "pure".

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”.
I admit it’s confusing to see it described as “pure function” and I suggest you to read the documentation (https://reactjs.org) to get a sense of how React components tend to look."

mpw added some commits Jan 2, 2019

Update Readme: remove "pure" from pure function
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"
Merge pull request #1 from mpw/not-so-pure
Update Readme:  remove "pure" from pure function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment