Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: fix #189 remove the redundant uncaught error and error stack trace from the console #191
fix: fix #189 remove the redundant uncaught error and error stack trace from the console #191
Changes from all commits
1cb275b
08bb7fc
bcc460f
195a724
a14b929
0e6bd3b
abca669
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
We can't do this. It would break uncaught exception behavior (see facebook/react#28515) and cause a memory leak (since
window
would have a reference to this error boundary instance and anything that it references as well).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.
Moving forward, I guess I would dive deeper into the React Internals and try to understand how the error handling works in there. Thanks.
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.
This got lost in a previous round of discussion, but the
default
andelse
cases here potentially break the generic signature above.Let's say we had a custom error type (e.g.
class MyCustomError extends Error
) that had some additional information in it. Let's say error handling code special handled this custom error type (e.g.error instanceof MyCustomError
). We'd break that logic in these two cases because we instantiate a vanillaError
.This might be an unlikely case but I think it's probably still not good for us to have a misleading generic type. That being said, I don't think this generic type is actually really doing anything that useful and we can just remove it entirely.
As a small efficiency nit too, I think we could lift the
suppressLoggingForError
method to the module level.So...