From 0619a5c0b47679293d5c5a5bb4a5e2925d79f8fe Mon Sep 17 00:00:00 2001 From: nicohrubec Date: Mon, 26 Aug 2024 11:23:36 +0200 Subject: [PATCH] Address pr comments --- .../getting-started-use/javascript.nestjs.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/platform-includes/getting-started-use/javascript.nestjs.mdx b/platform-includes/getting-started-use/javascript.nestjs.mdx index 973f690fcc72b..f45f9f1da4bb8 100644 --- a/platform-includes/getting-started-use/javascript.nestjs.mdx +++ b/platform-includes/getting-started-use/javascript.nestjs.mdx @@ -34,9 +34,9 @@ export class AppModule {} ``` In case you are using a global catch-all exception filter (which is either a filter registered with -`app.useGlobalFilters()` or a filter registered in your app module providers annotated with an empty `@Catch()` decorator), -add a `@WithSentry()` decorator to the `catch()` method of this global error filter. This decorator will report all -unexpected errors that are received by your global error filter to Sentry: +`app.useGlobalFilters()` or a filter registered in your app module providers annotated with a `@Catch()` decorator +without arguments), add a `@WithSentry()` decorator to the `catch()` method of this global error filter. This decorator +will report all unexpected errors that are received by your global error filter to Sentry: ```javascript {2, 6} import { Catch, ExceptionFilter } from '@nestjs/common'; @@ -52,7 +52,7 @@ export class YourCatchAllExceptionFilter implements ExceptionFilter { ``` In case you do not have a global catch-all exception filter, add the `SentryGlobalFilter` to the providers of your main -module. This filter will report all unhandled errors that are not caught by any other error filter to Sentry. +module. This filter will report all unhandled errors to Sentry that are not caught by any other error filter. **Important:** The `SentryGlobalFilter` needs to be registered before any other exception filters. ```javascript {3, 9}