Updated ignore errors

[skovhus]

No description provided.

[mattrobenolt]

Can you add this to the tests, please? :)

[skovhus]

@mattrobenolt sure, something like this?

[mattrobenolt]

Yup! That works. Thanks. 🍰

[skovhus]

@mattrobenolt two things:

i realize now that when adding a string to the whitelist filter, you don't start the regexp with a ^ or end it with $, e.g. the string can appear anywhere in the exception message. So:

globalOptions.ignoreErrors.push('Script error.');
globalOptions.ignoreErrors.push('Script error');

Is actually covering ... Javascript error: Script error on line ... error already. But also This is a script error that should be handled...... : /

Is this deliberately? It is rather confusing. Maybe this also confused when writing the two rules as the first rule is covered by the second one.

The thing I don't understand is why these errors still end up in Sentry... Testing locally by throw new Error('Javascript error: Script error on line 0')shows that the current default whitelist in raven-js works, but in production it ends up in Sentry. Any thoughts?

[skovhus]

@mattrobenolt Any comments?