ignoreErrors string inputs match on partials

[hotNoder]

ignoreErrors supports normal string and regexp, while I think it's not necessary to support normal string.
when I set ignoreErrors = ['some error'], I meant to ignore the exact message 'some error', but not 'some error XX' or 'XX some error'.
I know I can change ignoreErrors to [/^some error$/], but that meanwhile supports my point of view.
In sum, I think normal string here is somewhat misunderstanding.

[kamilogorek]

I'm not sure about this. Although it sounds fair, both scenarios can be achieved in both cases.

With partial match:
/^some error$/ => exact message
'some error' => partial match

Without partial match:
'some error' => exact message
/some error/ => partial match

Changing this would require a major bump, as there definitely are people who are relying on partial matching right now.

[benvinegar]

We should clarify in docs that strings are partial matches, and that you can use regexes to achieve explicit pattern matching. That should be sufficient; it's not clear to me that one set of behavior is more expected than the other.

[cseas]

We should clarify in docs that strings are partial matches

Why is this not mentioned anymore in the latest docs?
https://docs.sentry.io/platforms/javascript/configuration/filtering/#using-platformidentifier-nameignore-errors-
I was looking at these docs and was confused whether strings did a partial or exact match. Eventually ended up here.

[mydea]

We should clarify in docs that strings are partial matches

Why is this not mentioned anymore in the latest docs? https://docs.sentry.io/platforms/javascript/configuration/filtering/#using-platformidentifier-nameignore-errors- I was looking at these docs and was confused whether strings did a partial or exact match. Eventually ended up here.

Ah, I guess we missed this at this place (this is mentioned in a few different places in the docs 😬 ) - I'll update it there, thanks for mentioning: getsentry/sentry-docs#7668