You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases when it’s impossible to catch an error.
For example:
setTimeout(()=>{thrownewError('Boom');});
This may happen inside a third party library that user has no access to. We should have some way to ignore errors by message (at least if localStorage is available for the blacklist).
The text was updated successfully, but these errors were encountered:
When you say ignore, do you mean a hotkey to "ignore this error in the future"? Or a file/package.json entry to ignore regex matches?
Should we just ignore errors that have no stack traces to our application? I think that makes the most sense -- or at least show them up as if they're a warning (when we make the warning overlay, which is more like a warning toaster).
Looks like feature described in the OP ("We should have some way to ignore errors by message") didn't get implemented. I'd still like that feature. Should I open a new issue, or could we just reopen this one?
lockbot
locked and limited conversation to collaborators
Jan 14, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are cases when it’s impossible to catch an error.
For example:
This may happen inside a third party library that user has no access to. We should have some way to ignore errors by message (at least if
localStorage
is available for the blacklist).The text was updated successfully, but these errors were encountered: