-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: Refactor breadcrumbs integration to allow for custom handlers #2317
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
Conversation
262f201
to
4b898f9
Compare
4b898f9
to
d9fd340
Compare
@@ -1,23 +1,23 @@ | |||
// TODO: Rename this whole file to `instrument.ts` and make a distinction between instrumenting (wrapping the API) |
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.
Let’s mark it as deprecated, so we can remove it with v6
// [key in InstrumentHandlerType]?: boolean; | ||
|
||
/** JSDoc */ | ||
interface BreadcrumbIntegrations { |
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.
Also, add depreate here, the name should become something like, InstrumentOptions
// Dynamic keys like the one below doesn't work with interfaces :( | ||
// [key in InstrumentHandlerType]?: boolean; | ||
|
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.
I think we can remove this
does this fix #2125? |
Not yet, sorry https://github.com/getsentry/sentry-javascript/pull/2317/files#diff-8ac38be8ae7b14923c24ee27c747794cR194-R199 In order to unify dom breadcrumbs as well, this has to be corrected - #2299 |
No description provided.