You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need error reducers to intercept error events, not just those gracefully returned by failure(...). This means adding a catch statement on the effect, but as I outlined over here, I can't just swallow every error. That means conditionally re-throwing after dispatch is done.
The only way that's possible is through async generator functions.
Hmm, speed bump. I had assumed the only noticeable effect would be if you call the action directly (without a redux dispatch), but while implementing the change, I realized the return value of dispatch changes to a promise. This would implicitly require all synchronous actions to return promises. I'm not comfortable with that tradeoff.
I'm using the new synchronous generator feature exposed by PR #211. This
allows me to detect and report errors without swallowing them.
Breaking change: all errors trigger the `handleAction.error(...)` code
path, not just `failure(...)` return values. This also means it's much
harder to test action creators in isolation (as evidenced by the failing
tests in the examples/ directory).
Issue #205
I need error reducers to intercept error events, not just those gracefully returned by
failure(...)
. This means adding a catch statement on the effect, but as I outlined over here, I can't just swallow every error. That means conditionally re-throwing after dispatch is done.The only way that's possible is through async generator functions.
The text was updated successfully, but these errors were encountered: