redux-essentials-example-app VS react-error-boundary

You're right, it is related. But I think that Flux- and ELM-like architectures are making it even worse by forcing any "external" interaction to became the gap. Look how they suffer when it comes to executing any async operation like network request. Initially we have this relatively simple framework, but then we had to add "Middleware" to just run network request (which is a good example of the Remainder issue). I love the idea behind these architectures, which makes logic more predictable and testing way easier. I even was using them by myself. But now they looks like something turned inside out for me. I believe we could do better. I'm finishing my proposal right now. It will take couple more weeks to edit and translate it, but soon I'll show what I mean.

Hi, I maintain Redux and wrote most of our docs (including our current tutorials).

Can you give some details on which parts of our docs you feel are "incomprehensible"? I'm curious which specific pages you've been looking at, and for what purpose.

We've tried to organize the docs using the "Documentation System" approach described at [0]: Tutorials for teaching step-by-step, Explanations and How-To guides for specific topics, and References for API details.

Generally we want people to go through our "Redux Essentials" tutorial [1] as the primary way to learn how to use Redux correctly. It teaches "modern Redux" patterns with Redux Toolkit as the standard way to write Redux logic (including RTK Query for handling data fetching), and React-Redux hooks in components.

I'm genuinely interested in feedback on what explanations aren't clear and how we can improve things!

[0] https://documentation.divio.com/

[1] https://redux.js.org/tutorials/essentials/part-1-overview-co...

https://redux.js.org/tutorials/essentials/part-1-overview-concepts (covers how to use Redux Toolkit and RTK Query)

I use the use-error-boundary module for this just to never have to write a class component myself!

Requires a dependency but you can absolutely use error boundaries with functional components via react-error-boundary: https://github.com/bvaughn/react-error-boundary

as for checking errors: https://github.com/bvaughn/react-error-boundary

For those of you, who hate re-inventing the wheel or just prefer libraries for already solved problems, there is a nice one that implements a flexible ErrorBoundary component and has a few useful utils similar to those described above: GitHub - bvaughn/react-error-boundary

Use https://github.com/bvaughn/react-error-boundary for error boundaries and you won't have to write one yourself.

There's no reason to manually write an error boundary as a class component yourself, either, given that https://github.com/bvaughn/react-error-boundary exists.

Yeah, and even in that case, you should probably be using https://github.com/bvaughn/react-error-boundary rather than writing your own from scratch.

they can https://github.com/bvaughn/react-error-boundary (this is from the react team) doesn't matter how it works internally, im not going to write a class just for error handling.

i would not bother with classes tbh, use this: https://github.com/bvaughn/react-error-boundary it's made by a react core team member and they even recommend it.