actions and dispatch about react-redux

[gnoff]

in #16 the binding of action creators happens during mounting only one time.

If you want to pass all app actions to all subcomponents using the new api you can do so trivially by passing all of your actions into the second argument (see example below). We wouldn't want to do that for you automatically however since it would cut off other use cases and possibly pollute connected components with unnecessary or redundant actions (imagine nested connected components for a email client where you have navigational actions for what messages are being viewed but then a component for the actual message detail view, not that this would be the optimal setup)

@connect(
  State => State,
  require('./path/to/module/that/contains/allActions')
)

[gaearon]

That's exactly the intention for the new API. It is connect(selectState, mapDispatch, mergeProps). While selectState is called every time store state changes, mapDispatch is only called once.

[maxguzenski]

Yes, but it looks like that you have to pass actions on @connect, why not and @connect just pass it forward all the time?

[gnoff]

Actions are attached to connected components as props. Passing all actions all the time would unnecessarily pollute props of all connected components and would greatly increase the likelihood of overloading a prop and hiding an intended behavior. In more complicated apps it doesn't make sense for all components to be aware of all actions and therefore this behavior you suggest would hinder the majority for the convenience of a few