gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix typos and add clarification to mapStateToProps (#18629)

Browse Source
This commit is contained in:
Colin Crawford
2018-10-15 14:02:19 -04:00
committed by Jonathan Grah
parent 6d7f3566d7
commit c8abc30c8d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
client/src/pages/guide/english/redux/reselect/index.md
View File

@ -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 efficient. A selector is not recomputed unless one of its arguments changes.
* Selectors are composable. They can be used as input to other selectors. * 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: #### More Information:
<!-- Please add any articles you think might be helpful to read before writing the article --> <!-- Please add any articles you think might be helpful to read before writing the article -->