From c8abc30c8da7ad5d5c6169a59dabbe54bde67e4a Mon Sep 17 00:00:00 2001 From: Colin Crawford Date: Mon, 15 Oct 2018 14:02:19 -0400 Subject: [PATCH] fix typos and add clarification to mapStateToProps (#18629) --- client/src/pages/guide/english/redux/reselect/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/src/pages/guide/english/redux/reselect/index.md b/client/src/pages/guide/english/redux/reselect/index.md index 18052beda3..4e3161f7bb 100644 --- a/client/src/pages/guide/english/redux/reselect/index.md +++ b/client/src/pages/guide/english/redux/reselect/index.md @@ -9,7 +9,7 @@ Why do we need selectors? Official docs describe it this way: * Selectors are efficient. A selector is not recomputed unless one of its arguments changes. * Selectors are composable. They can be used as input to other selectors. -It might sound complicated but selectors allow your app to work faster by reducing unnecessary rerendering(s). Normally `mapStateToProps` is called every single time any change in `store` is made. `mapStateToProps` binds store values to react. Until you use `PureComponents` it might cause component being rerendered although it's not required. +It might sound complicated but selectors allow your app to work faster by reducing unnecessary rerendering(s). Normally `mapStateToProps` is called every single time any change in `store` is made. React-redux's "connect" function uses a `mapStateToProps` function argument to specify which store values to pass to the connected react component as props. Until you use `PureComponents` it might cause component being rerendered although it's not required. #### More Information: