getting to know redux

So we’ve got this big project at work. I’m trucking along la la la. And it becomes obvious — parts of our application will need a global state. A gal can only lift local state so far.

We knew this. We knew that we’d probably go to reduxjs. So I sat down to do the tutorial.

I was AGHAST. I was going to have to write how much boiler plate? All caps enums describing actions over and over and over and over. And they wanted the redux store object shape to be HOW FLAT?

Redux is supposed to be simple in its concept. But I didn’t expect so much ugly code in implementing its structures.

I did the tutorial, dutifully. I was pretty damn angry with just the basic example ToDos app used app in the redux world. And then I started delving into the “Advanced Tutorial”. Which covered things I really need — async flow, with examples of rest api calls.

And then found something that offered relief from ugly code. The Reducing Boilerplate section. Which seemed like inviting me to invent an unnecessary replacement for a wheel. Sometimes developing an opinion isn’t worth the trouble.

I’m not sure where I found the link in the mishmash of organization of the official ReduxJs site. But enter: Redux Toolkit. Ok. Less boilerplate. Sane descriptions. I can live with this.