Could mapStateToProps be an object?

I’m playing around with selectors, and most of my mapStateToProps functions look like this:

const mapStateToProps = state => ({
  isAuthenticated: selectors.isAuthenticated(state),
  isSomethingElse: selectors.isSomethingElse(state),
});

Since I always pass on the state, would it be okay to do the same thing as mapDispatchToProps does, and just allow sending an object of functions? Like so:

const mapStateToProps = {
  isAuthenticated: selectors.isAuthenticated,
  isSomethingElse: selectors.isSomethingElse,
};

Then, connect could do the work required to call each of these with the state.

I’d be happy to submit a PR doing this - but what are your thoughts? I’m sure there’s a reason the API is the way it is 😃

[markerikson]

Part of me still kinda wants do to this, but I’ll go along with Tim and say it’s not worth it to build it in.

[markerikson]

I’m willing to potentially reconsider this as long as we keep it narrowly scoped in behavior and implementation.

No factory functions. No nesting.

I can see two useful forms:

• An array of string key names
• An object of selectors

Both are doable if we keep the behavior limited to basically what @jchook showed. Question is, whether there’s enough benefit for including that functionality.

Tweeted this question: https://twitter.com/acemarke/status/1087568080052596736

I’ll reopen this issue for the sake of discussion.