RFC - Remove all current binding functions except for Hooks

I’m thinking about a bold breaking change.

After this awesome PR by @d3x7r0, you can use Redux Zero with a really small API, based on Hooks:

const Counter = () => {
  const store = useStore();
  const count = useSelector(({ count }) => count);
  const increment = useAction(({ count }) => ({ count: count + 1 }));

  return (
    <>
      <p>Count: {count}</p>
      <button onClick={increment}>Increment</button>
    </>
  )
}

With that, it seems that the other approaches (connect and Connect) simply don’t make sense anymore. I’m highly considering rebranding Redux Zero to be all about this three hooks. No more, no less.

What do you think?

[matheusml]

Hey @makinde, thanks for the feedback.

No, classes don’t support hooks. So the reason why I want to go all-in into hooks only API is:

1. That’s where React itself is going
2. I don’t think that having two ways of doing the same thing is beneficial. Because you’ll have more API to learn, more code to maintain and bigger bundle size

I’m already building some experiments to drop support with Connect/connect and go all-in into hooks. And maybe even rebranding the project.

[makinde]

Thanks for responding. You should definitely feel empowered to direct things as you see best.

I’ll just quickly highlight some of what you gain with the current “redux-like” branding and messaging. Because I know that this library is supposed to be like redux, I can depend on their docs. For instance, I’m trying to learn middleware in redux-zero right now. The docs are…brief, to say the least. But because it is so similar to the redux concept, I can rely on the tons of documents and blog posts about the topic.

Just something to keep in mind as you consider diverging from redux in the future. Thanks for all the hard work on the tool!