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
After an error occurs, the effect stops. One possible solution is to refrain from catching errors within the action pipe and instead catch them in the HTTP response stream, as illustrated below:
Which @ngneat/effects-* package(s) are the source of the bug?
effects-ng
Is this a regression?
No
Description
Operator
catchError
in effects is not working and after throwing an error, the effect stops emitting. Please see full example in stackblitz.This is related to #34. I think this applies to effect functions as well, see
createEffectFn
implementation.Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-tvg994?file=src%2Fmain.ts
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
No
The text was updated successfully, but these errors were encountered: