ueman / sentry-dart-tools

Collections of various Sentry integrations for Dart/Flutter

Hi there 👋

Finde me at uekoetter.dev

sentry-dart-tools's Issues

Improve GraphQL integration

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

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

Check whether bindings are already initialized

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

GraphQL errors: // we couldn't format it nicely

@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

GraphQL errors should have their name as type

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

Support GraphQLs nested exceptions

Currently they look like that

Use custom widgets binding

See getsentry/sentry-dart#1184