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
Which @ngneat/effects-* package(s) are the source of the bug?
effects-ng
Is this a regression?
Yes
Description
I have angular upgraded from 13 to 15. I am using effects-ng for http requests.
In case I have http error I can't get the error response in tapResult's error callback and can't intercept this error inside angular error interceptor.
Is there a problem with compatibility or something else?
For example I'm getting error 404 from server but code in tapResult's error callback doesn't invokes. And the most important problem is that I can't intercept this error.
In previous version of angular (v13) everything worked fine.
Which @ngneat/effects-* package(s) are the source of the bug?
effects-ng
Is this a regression?
Yes
Description
I have angular upgraded from 13 to 15. I am using effects-ng for http requests.
In case I have http error I can't get the error response in tapResult's error callback and can't intercept this error inside angular error interceptor.
Is there a problem with compatibility or something else?
For example I'm getting error 404 from server but code in tapResult's error callback doesn't invokes. And the most important problem is that I can't intercept this error.
In previous version of angular (v13) everything worked fine.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in
The text was updated successfully, but these errors were encountered: