Feedback for “useSentry”

Hi everyone
I have been wondering for a few hours how to manage errors with Sentry
I want to avoid reporting USER_NOT_FOUND on the Login or INCORRECT_PASSWORD
or validation fileds

- https://pothos-graphql.dev/docs/plugins/validation
- GraphQLError and ZodError

` new GraphQLError('User not registered', {
extensions: {
code: 'USER_NOT_FOUND',
},
})`

#DOC
https://the-guild.dev/graphql/envelop/plugins/use-sentry

- skipError (default: ignored EnvelopError) - Indicates whether or not to skip Sentry exception reporting for a given error. By default, this plugin skips all EnvelopError errors and does not report it to Sentry.

but

```
/**
* Indicates whether or not to skip Sentry exception reporting for a given error.
* By default, this plugin skips all `GraphQLError` errors and does not report it to Sentry.
*/
skipError?: (args: Error) => boolean;
```

I would like to use GraphQLError to report with Sentry when you really need
how I have to use the skipError function
If someone can help me at the confused
thx

Start with the useSentry documentation and the skipError option, then compare the documented default for EnvelopError with the shown GraphQLError type. A complete documentation change would explain how to handle USER_NOT_FOUND, INCORRECT_PASSWORD, validation errors, GraphQLError, and ZodError reporting.

Written by the indexing model from the issue text.