Closed brettski closed 1 year ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
that.us | ✅ Ready (Inspect) | Visit Preview | Jul 18, 2023 1:30pm |
This pull request has been deployed and Sentry has observed the following issues:
<anonymous>(src/_dataSources/api.that.tech/util...
View Issue<anonymous>(src/_dataSources/api.that.tech/util...
View Issue<anonymous>(src/_dataSources/api.that.tech/util...
View Issue<anonymous>(src/_dataSources/api.that.tech/util...
View Issue<anonymous>(src/_dataSources/api.that.tech/util...
View IssueDid you find this useful? React with a 👍 or 👎
v3.11.10
Ensures instance of error is passed to sentry. Corrects the errors in Sentry:
Object captured as exception with keys: extensions, message, path
Errors passed from GraphQL are not an instance of error which is causing an exception in Sentry when using
captureException
. This corrects that by checking first. True, for errors which are being created here don't have a stack trace, but they didn't to start with as it was on an object from GraphQL to begin with. The details of the error are still written to Sentry context.