mirror of
https://github.com/trezor/trezor-suite.git
synced 2026-02-20 00:33:07 +01:00
chore(sentry): code commentary about SDK IPC
This commit is contained in:
committed by
Jiri Zbytovsky
parent
2d2ee98846
commit
e1c3cd9fcb
@@ -27,7 +27,7 @@ export const allowedDomains = [
|
||||
'api.dropboxapi.com',
|
||||
'content.dropboxapi.com',
|
||||
'notify.dropboxapi.com',
|
||||
'o117836.ingest.sentry.io',
|
||||
'o117836.ingest.sentry.io', // TODO is this needed? Seems that the Sentry SDK bypasses interceptor
|
||||
'oauth2.googleapis.com',
|
||||
'googleapis.com',
|
||||
onionDomain,
|
||||
|
||||
@@ -22,6 +22,11 @@ export const withSentryScope = Sentry.withScope;
|
||||
|
||||
export const captureSentryMessage = Sentry.captureMessage;
|
||||
|
||||
/**
|
||||
* Sets a tag to allow or disallow sending Sentry reports. Until then, they are sent, but heavily redacted, see redactSentryEvent function.
|
||||
* Note that in case of Suite Desktop, Sentry tags are shared between Renderer and Main process, sentry has its own IPC:
|
||||
* https://docs.sentry.io/platforms/javascript/guides/electron/features/inter-process-communication/,
|
||||
*/
|
||||
export const allowSentryReport = (value: boolean) => {
|
||||
Sentry.setTag(ALLOW_REPORT_TAG, value);
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user