ueman / sentry-dart-tools Goto Github PK

This can be done via https://api.flutter.dev/flutter/foundation/BindingBase/debugBindingType.html

The GraphQL can be improved after the following two issues are being worked on:

• getsentry/sentry#38913
• getsentry/sentry#33723

pubspec.yaml

dependencies:
  ...
  sentry_link: ^0.3.0
  sentry_logging: ^8.0.0

Because sentry_logging >=8.0.0 depends on sentry 8.0.0 and sentry_link 0.3.0 depends on sentry ^7.8.0, sentry_logging
  >=8.0.0 is incompatible with sentry_link 0.3.0.
And because no versions of sentry_link match >0.3.0 <0.4.0, sentry_logging >=8.0.0 is incompatible with sentry_link
  ^0.3.0.

@ueman thanks for this! It's exactly what I needed for our Sentry setup.

I've noticed that my GraphQL errors are getting reported to Sentry as <unlabeled event>s

Digging in a bit it seems like errors.toSentryExceptions(request, response) is failing to return exceptions so we hit the // we couldn't format it nicely block.

I'm testing with a fairly simple error just to verify everything is setup correctly.

{
  "errors": [
    {
      "message": "Sentry test",
      "path": ["testPath"],
      "extensions": { "code": "INTERNAL_SERVER_ERROR" }
    }
  ],
  "data": { "testPath": null, "__typename": "Mutation" }
}

Here's a screenshot from the debugger. the exceptions will be empty here so we end up in the else block

See getsentry/sentry-dart#1184

After this change there will be no more catch all GraphQLError exception. As a result, errors should be more granular and easier to find.

Currently they look like that