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
{{ message }}
This repository has been archived by the owner on Sep 10, 2022. It is now read-only.
It would be nice to have an error boundary React 16 HoC. While most of us will have at most one in our entire app and might be overkill, I'm interested in exploring multiple and it would be really handy if we had an easy way to define those, hence I'm here ¯_(ツ)_/¯.
Between lifecycle and branch it could easily be done, the only missing question would be how to handle the case when we want to run arbitrary code (i.e error reporting).
What do you think? Does it fall within the scope of this library?
The text was updated successfully, but these errors were encountered:
It would be nice to have an error boundary React 16 HoC. While most of us will have at most one in our entire app and might be overkill, I'm interested in exploring multiple and it would be really handy if we had an easy way to define those, hence I'm here ¯_(ツ)_/¯.
Between
lifecycle
andbranch
it could easily be done, the only missing question would be how to handle the case when we want to run arbitrary code (i.e error reporting).What do you think? Does it fall within the scope of this library?
The text was updated successfully, but these errors were encountered: