-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom exception does not work in SentryInterceptor #100
Comments
I think that pr #95 is wrong. I think |
@daniel-tmp it's possible to revert this? |
As it is now, if you have multiple filters, it always reported to Senty all errors because this code always returns true: return filters.some(({ type, filter }) => {
return !(exception instanceof type && (!filter || filter(exception)));
}); Example: new SentryInterceptor({filters: [
{
type: HttpException,
filter: (exception: HttpException) => {
return (500 > exception.getStatus());
},
},
{
type: MyCustomError
}
]})
It mus't be reverted to use |
did this get reverted? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I'm able to intercept exceptions using the example that exists in docs:
But when I try to track custom exception sentry interceptor does not work properly:
Another thing that I found is when I evaluate exception status it works:
This is the definition of CustomHttpException:
The text was updated successfully, but these errors were encountered: