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
feat(core): Add dropEvent
options to moduleMetadataIntegration
#11718
base: develop
Are you sure you want to change the base?
Conversation
size-limit report 📦
|
enableSend: true, | ||
stackParser, | ||
integrations: [ | ||
moduleMetadataIntegration({ dropEvent: { ifNoStackFrameMetadataMatches: m => m?.team === 'backend' } }), |
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.
moduleMetadataIntegration({ dropEvent: { ifNoStackFrameMetadataMatches: m => m?.team === 'backend' } }), | |
moduleMetadataIntegration({ dropEvent: { ifNoStackFrameMetadataMatches: m => m.team === 'backend' } }), |
or can m
be undefined here?
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've changed the types to reflect that the parameter can be undefined. This allows users to filter on whether the metadata for a frame is defined!
This additional option can be used to drop events that don't match specific module metadata on any stack frames: