DEV Community

React, Redux, and API's Part Three: Redux

Patrick on November 05, 2018

original post can be found on my blog In the last post we looked a bit deeper in to using React to talk to APIs in a DRY manner. In this post, we ...
Read full post
Collapse
 
markerikson profile image
Mark Erikson •

FWIW, I recommend against passing in the action creators under a props.actions object, for two reasons:

  • It sorta makes the component "aware" of Redux when you're specifically labeling those functions as "actions"
  • More specifically, it means you have to actually write a mapDispatch function instead of using the "object shorthand" for binding the action creators. See our new React-Redux docs page on using mapDispatch for more details on the various ways this can work, including the "object shorthand" that we recommend.
Collapse
 
patrickgordon profile image
Patrick •

Hey Mark,

Thanks for the interesting comment - I actually wasn't aware of the new object shorthand. That looks really interesting.

I'd be curious to hear your thoughts more about why it matters if the component is 'aware' of redux. I would say the main reason we use the props.actions object is just for consistency and tidiness.

Cheers for engaging, I appreciate it!

Collapse
 
markerikson profile image
Mark Erikson •

Thing is, the "object shorthand" isn't new at all - it's been there since day 1 :) See react-redux issue #1 for early discussion. It's even in the existing API docs, but it's kinda buried in there, and you have to squint hard at the right paragraph to understand it.

The "awareness" thing is mostly a general principle. I think it's worth trying to keep most components generic and reusable in the sense that they shouldn't care where their props are coming from. It's not always achievable, but it's a useful long-term architectural objective.

Thread Thread
 
patrickgordon profile image
Patrick •

Well, you learn something new every day!

Thanks for the insight, Mark!