feat: Include exception type in ignoreErrors tests

[kamilogorek]

Ref #1005 and #1007

[mitsuhiko]

For what it's worth I think we should support that being a function instead of regexp optionally.

[benvinegar]

My expectation would be that we append type and message together, and run the regex on that.

e.g. if you have type ReferenceError, and message foo is not defined, we'd run the regex against: ReferenceError: foo is not defined

No? What do other client libs do here? @mitsuhiko

[kamilogorek]

@benvinegar only Ruby and Python have some sort of ignore options, and both of those SDKs use exception type only.

The reason why I didn't want to append them together, is that : in between. Although I'm almost sure that all the browsers show messages in the same type + ': ' + message format.

[kamilogorek]

@benvinegar updated.
@mitsuhiko agree on the function usage, but it'd also require extracting global errors to a separate array, as they should always be used:

// "Script error." is hard coded into browsers for errors that it can't read.
// this is the result of a script being pulled in from an external domain and CORS.
globalOptions.ignoreErrors.push(/^Script error\.?$/);
globalOptions.ignoreErrors.push(/^Javascript error: Script error\.? on line 0$/);

Let's keep this feature in a separate issue.

[benvinegar]

The reason why I didn't want to append them together, is that : in between.

Yeah, I hear you. But I think everyone just expected it to work this way (I for one thought it did).

[benvinegar]

We should also keep in mind that if people were doing this: /^Strictly the message without type$/, those regexes will no longer work.

[kamilogorek]

True that, I missed that scenario. Hopefully most of people are using string based tests.