You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This becomes even more annoying when you also want to add pluggable intergations, as then instead of this: integrations: [Sentry.replayIntegration()] you suddenly have to do this:
You can fully opt-out of default integrations via defaultIntegrations: false. In addition to this, we can allow users to pass an object, which allows to disable individual keys:
Sentry.init({defaultIntegrations: {'InboundFilters': false,'GlobalHandlers': false},// you can then continue to add integrations as normallyintegrations: [Sentry.replayIntegration()]});
This would be backwards compatible, but simply be a new and easier way to solve this problem.
The text was updated successfully, but these errors were encountered:
Description
Today, it is rather annoying to opt-out of individual default integrations. You have to do something like this:
This becomes even more annoying when you also want to add pluggable intergations, as then instead of this:
integrations: [Sentry.replayIntegration()]
you suddenly have to do this:which really does not feel ideal.
I propose to add a new way to disable individual default integrations, similar to how https://www.npmjs.com/package/@opentelemetry/auto-instrumentations-node does this:
You can fully opt-out of default integrations via
defaultIntegrations: false
. In addition to this, we can allow users to pass an object, which allows to disable individual keys:This would be backwards compatible, but simply be a new and easier way to solve this problem.
The text was updated successfully, but these errors were encountered: