-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(PE-5263): ignore errors from unknown extension #404
Conversation
Visit the preview URL for this PR (updated for commit 83bd686): https://arns-portal--pr404-pe-5263-filter-chrom-lbwkg3an.web.app (expires Fri, 26 Jan 2024 21:02:56 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 1f59769442cb89cf2a92042a342e51fe94047b94 |
70010ff
to
ee6d8fb
Compare
src/utils/sentry.ts
Outdated
return sanitizeEvent(event); | ||
}, | ||
}) | ||
: {}; | ||
|
||
export default sentry; | ||
|
||
const sanitizeEvent = (event: Sentry.Event): Sentry.Event => { | ||
const filterMessages = new Set([ | ||
'chrome-extension://aflkmfhebedbjioipglgcbcmnbpgliof/injected.js', |
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.
is this the best way to ignore extensions?
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.
Possibly. I was getting this as the method for ignoring messages, there may be a better way to ignore an actually extension specifically.
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.
Actually I just realized, with new releases of the extension, this would break. More durable to check for the error message I suppose.
5c43982
to
83bd686
Compare
No description provided.