-
Notifications
You must be signed in to change notification settings - Fork 47.5k
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
Error boundries should not unmount composite components which were not mounted. #5982
Error boundries should not unmount composite components which were not mounted. #5982
Conversation
} | ||
|
||
render() { | ||
if(!this.state.error) return <div>{this.props.children}</div>; |
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.
space after if
What happened before? Also, can you unmount the whole thing as part of the test too? |
When do we get our linter back??? I suppose we always have @spicyj the human linter for when babel-eslint is broken and throwing exceptions. Before, we attempted to unmount the composite children and things would blow up with an NPE if the error had a composite sibling occurring after the angry component. |
18c085d
to
86305fb
Compare
@jimfb updated the pull request. |
So we still fail if componentWillUnmount throws somewhere in the subtree – is that right? |
k |
Eww, Correct. |
Error boundries should not unmount composite components which were not mounted.
We'll need to fix that. |
Error boundries should not unmount composite components which were not mounted.
Fixes #5980
cc @spicyj