From f41764af35d03de4ef6b2f6e567302ed48f2b631 Mon Sep 17 00:00:00 2001 From: Jonathan Gold Date: Mon, 17 Dec 2018 11:12:43 -0500 Subject: [PATCH] docs/using-react-redux: Fixes substition of `mapDispatchToProps` with `mapStateToProps` My first read of the docs as currently written is that they incorrectly use the term `mapStateToProps` instead of `mapDispatchToProps` in the answer to "Can I mapDispatchToProps without mapStateToProps in Redux?" This version fixes that, assuming my reading is correct. --- .../connect-dispatching-actions-with-mapDispatchToProps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using-react-redux/connect-dispatching-actions-with-mapDispatchToProps.md b/docs/using-react-redux/connect-dispatching-actions-with-mapDispatchToProps.md index a501188c3..c88793f24 100644 --- a/docs/using-react-redux/connect-dispatching-actions-with-mapDispatchToProps.md +++ b/docs/using-react-redux/connect-dispatching-actions-with-mapDispatchToProps.md @@ -374,7 +374,7 @@ There are discussions regarding whether to provide `dispatch` to your components ### Can I `mapDispatchToProps` without `mapStateToProps` in Redux? -Yes. You can skip the first parameter by passing `undefined` or `null`. Your component will not subscribe to the store, and will still receive the dispatch props defined by `mapStateToProps`. +Yes. You can skip the first parameter by passing `undefined` or `null`. Your component will not subscribe to the store, and will still receive the dispatch props defined by `mapDispatchToProps`. ```js connect(