-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ref(core): Improve event mechanism
for supabase integration
#17286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
@@ -448,6 +454,7 @@ function instrumentPostgRESTFilterBuilder(PostgRESTFilterBuilder: PostgRESTFilte | |||
return res; | |||
}, | |||
(err: Error) => { | |||
// TODO: shouldn't we capture this error? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@onurtemizkan not sure if this is me missing something or if we should call captureException
here. Can you take a look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, looks like this comes from the original implementation we ported:
I don't see a reason why we should not capture this, though.
@@ -236,6 +236,7 @@ function instrumentAuthOperation(operation: AuthOperationFn, isAdmin = false): A | |||
captureException(res.error, { | |||
mechanism: { | |||
handled: false, | |||
type: 'auto.db.supabase.auth', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these types are one level more specific than the trace origin on the spans (auto.db.supabase
). I think this is fine.
ref: #17250
ref: #17212