4 ms·
I had to rescue a redux-saga project that went badly off the rails. It was one of the most inscrutable and difficult to debug codebases I've ever had to work wi
by cageface 4y ago
I had to rescue a redux-saga project that went badly off the rails. It was one of the most inscrutable and difficult to debug codebases I've ever had to work with. Forget completely about ever having a usable stack trace.
- bayesian_horse 4y agoYes, I guess you can abuse every technology. Sagas are always sideeffects and thus have to be used with restraint. Sagas keep state (and you should keep most state in the redux store, anyway). So, yes, you can go wrong, as with everything else. But it's better than using useEffect as an async framework.