I cringe when I see .then(() => dispatch(...)).catch(...) in React projects. If a component throws during dispatch, you’ll get into catch.
-
-
How? When people have catch() in AJAX response in apps in 99% cases they mean to catch *that* error.
1 reply 1 retweet 1 like -
Replying to @dan_abramov @sophistifunk
When React component throws it is always user error. It corrupts React internal state too. There is no graceful handling it.
1 reply 0 retweets 1 like -
Replying to @dan_abramov
Sorry to interject. Think I have this: react-css-modules throws by default; next render gives __reactInternalInstance error.
1 reply 0 retweets 0 likes -
Replying to @sebinsua @dan_abramov
Is that the kind of React internal state instance problem you would expect to see after an earlier render failed?
2 replies 0 retweets 1 like
A difficult debugging experience: if you write logic to render these errors, you swallow them. e.g. https://yelouafi.github.io/redux-saga/docs/basics/ErrorHandling.html …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.