Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
For context, I've used Redux before, as well as redux sagas, and I've even gone down the path of building a redux framework (I'll put a note at the end why I gave up with it), so I agree with problem statement that redux by itself has too much boiler plate.
I've created a repo here to demonstrate what I mean.
have you looked into https://github.com/pmndrs/zustand ? you don't need arbitrary structures for actions at all, neither do you need action types, or dispatch.
as for request, you should use suspense for that, routing this through your state manager is a mistake. this is all inbuilt into react now, loading, fallbacks, and composition is better done by react. your state manager could hold a url, but he fetching is done by something like this: https://github.com/pmndrs/suspend-react
FWIW, the app that I now work on for my day job, https://github.com/RecordReplay/devtools , is a great example of a truly complex client-side app that is not just data CRUD - it's a full JS debugger as an app, written with React and Redux. (In fact, it actually started as a fork of the Firefox DevTools codebase.)