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
Sometimes, you have a bad component which will throw an exception at render.
It seems like that once they throw, you cannot remount any component after it due to the unmountComponent which will itself throw for internalInstance._currentElement (undefined on internalInstance).
I don't really know how we could implement this, maybe by wrapping the render method like react-transform-catch-errors does it.
(I wonder if this should be there or in the Cosmos suite, I believe that it's kind of low-level so it should be for react-component-playground, right?).
The text was updated successfully, but these errors were encountered:
I think that I'm pretty sure I'm using react-transform-catch-errors on my playground configuration, but I admit that I could have got something wrong during the process.
Will double-check!
But nevertheless, why integrating at Cosmos level?
Sometimes, you have a bad component which will throw an exception at
render
.It seems like that once they throw, you cannot remount any component after it due to the
unmountComponent
which will itself throw forinternalInstance._currentElement
(undefined oninternalInstance
).I don't really know how we could implement this, maybe by wrapping the
render
method like react-transform-catch-errors does it.(I wonder if this should be there or in the Cosmos suite, I believe that it's kind of low-level so it should be for react-component-playground, right?).
The text was updated successfully, but these errors were encountered: