-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Export SpotlightBrowser
Sentry integration
#403
Comments
hey @Lms24 how about instead of exporting sentryBrowserIntegration, we add a User can send Sentry.client() in it and spotlight gets injected in that client, otherwise default way of injecting. it will be something like -
let me know if this sounds good to you, i'll push the code. |
This would be a possibility but unfortunately, it only fixes half the problem. For example, take the Spotlight Electron app. If people build a frontend application but want to use Spotlight with the app instead of the built-in overlay, there is no overlay that's injected into the frontend application. Meaning we couldn't pass a client to the electron app. We can however export the spotlightBrowserIntegration from Does this sound reasonable to you? |
Anyway, we can export the integration whenever we want; it's not a breaking change as long as we try to auto-inject the integration by default (which we do at the moment). I therefore removed it from the 2.0 milestone. |
Yup, this is good. |
Hmm yeah, maybe that's another angle. Let me think about it for a bit! |
Being done in getsentry/sentry-javascript#13263 |
This is now merged and released. Closing the ticket as we don't intend to export the built-in integration yet. One thing to watch out for is a potential clash between the SDK-side integration and the built-in integration: #511. |
If users run spotlight standalone/with the electron app, the current automatic
SpotlightBrowser
injection logic won't work. I propose we export thespotlightBrowserIntegration
from the@spotlightjs/overlay
and@spotlightjs/spotlight
packages so that users can register the integration themselves in their browser apps and don't have to rely on the auto injection mechanism.Important: We'll keep auto injection as-is (meaning it's on by default but can be deactivated). This is just an additional way to get events from the browser into spotlight.
Tasks
The text was updated successfully, but these errors were encountered: