-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
will the next next version coming with any mechanism of error processing #1266
Comments
Its not implemented atm. We could do it for v5 |
At first I thought this would be just optional try catch wrapper, but its not so simple, because Inferno uses native DOM events, and those will not be caught by simple try catch above diff routine. :/ I think this will not land in next release, maybe v7 |
is there any update on this feature request? or atleast a preferred way to handle uncaught errors in components? |
I think it depends a lot what you want to do ? Where does the error occur? |
Hi @Havunen , I was wondering now that |
Hi @abhi18av , Error processing has not been implemented. |
Oh, I see. Thanks for the quick revert. 👍
…________________________________
From: Sampo Kivistö <[email protected]>
Sent: Monday, March 16, 2020 11:52:19 AM
To: infernojs/inferno <[email protected]>
Cc: Abhinav Sharma <[email protected]>; Mention <[email protected]>
Subject: Re: [infernojs/inferno] will the next next version coming with any mechanism of error processing (#1266)
Hi @abhi18av<https://github.com/abhi18av> , Error processing has not been implemented.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1266 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADBU2XSTLIXH4YNRFDFSKCLRHXARXANCNFSM4EONFJQQ>.
|
https://reactjs.org/docs/error-boundaries.html
like this, same as ReactV16
The text was updated successfully, but these errors were encountered: