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 4 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.
Seems like this intentionally breaks the generics type for the hook. I guess you had to do this, to support the non-object case in
suppressLoggingForError
but if that's the case we should either remove the generic parameter fromsuppressLoggingForError
(since it's not a guarantee) or maybe change it to require extendingError
(so then the non-object case insuppressLoggingForError
would be unsupported from a types perspective at least)?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.
I am sorry, but I don't quite get this one. Why removing the generic parameter from
suppressLoggingForError
would be of help? I noticed that in the generic parameter ofuseErrorBoundary
,<TError = any>
, so I assumeTError
can be very flexible yet maintaining it can assure some basic type check. Please shed more light on this.