Redux – Not Dead Yet (2018)

Re:Redux – Not Dead Yet (2018) by runawaybottle on Thursday April 09, 2020 @10:52AM (#22823098)

Can you give me an example how you got to 400 actions? Just enumerate like 5 or so, I’m assuming you are building features where groups of actions are just necessary based on the patterns you are using.

I’m genuinely curious because I feel like this kind of inflation of actions/reducers in Redux is what makes it nightmarish.

[ Parent | on HN ]

Re:Redux – Not Dead Yet (2018) by jfengel on Thursday April 09, 2020 @11:07AM (#22823243)

For one thing they do encourage a lot of tiny actions. A frequent pattern I use requires three actions for every server call: one to trigger a saga, one when it succeeds, and one for when it fails.

The standard form is incredibly verbose, I've started to shift away from it.

[ Parent | on HN ]

Re:Redux – Not Dead Yet (2018) by acemarke on Thursday April 09, 2020 @11:33AM (#22823521)

Note that the new `createAsyncThunk` API in Redux Toolkit handles generating and dispatching the promise lifecycle actions for you [0]. Also, while sagas are a great power tool, most Redux apps don't need them [1].

[0] https://redux-toolkit.js.org/api/createAsyncThunk

[1] https://blog.isquaredsoftware.com/2020/02/blogged-answers-wh...

[ Parent | on HN ]

Re:Redux – Not Dead Yet (2018) by mikewhy on Thursday April 09, 2020 @01:22PM (#22824903)

Awesome! It's great to finally have some links to share.

The company I'm currently working with is the first time I've used sagas / observables / "anything async is through side effects". I've constantly been saying "this is madness, this giant block of code, all these concepts, all this room for things to go wrong, just to do a `fetch`?". It's also the first time in a few years of using redux I've had to deal with race conditions.

Edit: Oh, and you can even `await dispatch`! All the things I've been doing in Redux for years and told I shouldn't, now being officially endorsed.

[ Parent | on HN ]

Re:Redux – Not Dead Yet (2018) by majewsky on Thursday April 09, 2020 @04:59PM (#22827130)

Here's a real-world example, from an OpenStack dashboard developed in my team that uses React/Redux for some of the newer parts (most parts are still server-side only): https://github.com/sapcc/elektra/blob/e4d93bc601caa99cceb7ba...

That's 76 actions just for the NFS/CIFS-as-a-service UI.

(I'm not saying this is the best way to do it, but that's what's happening right now.)

[ Parent | on HN ]

Re:Redux – Not Dead Yet (2018) by onion2k on Thursday April 09, 2020 @11:16AM (#22823332)

Can you give me an example how you got to 400 actions?

I'm not going to go in to detail on HN, but the app I work on is used to make diagrams for the legal industry and to define how they change over time. It's sort of like Visio for lawyers, with a basic animation editor that understands the underlying data. There are a lot of actions simply because it does a lot of things that can't be generalised in to higher level actions (well, they could, but it'd be messy.)

[ Parent | on HN ]