-
Notifications
You must be signed in to change notification settings - Fork 120
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
Unmount state fix #114
Unmount state fix #114
Conversation
Your issue would mean that unmount is called while the component is in a state transition, which should not happen. What version of React is this? I'm afraid that by merging this PR we are bringing back the issue reported in #112. Let me try this out tonight and I'll let you know how it went. |
@JorgenEvens Any updates about this issue ? |
@zedissime I only had a quick look and was unable to reproduce the issue described. Letting me know which version of React you are using and maybe a small reproduction case would be helpful. |
@JorgenEvens I'm facing it in React |
@zedissime Thanks, I'm gonna try reproduce this later today. |
Just in case of, I did update React in 16.4.1 and it is still happening. |
It broke 🎉 |
Managed to check that this does not bring back #112. Thanks @xiaotian-tan for the bug report and @zedissime for some help on reproducing the issue. |
This PR is released as part of v3.1.2. |
I encountered issue when componentWillUnmount try to update active on undefined.
So I made small change to componentWillUnmount to make state updates safer.
A additional section in demo is added to demonstrate cached avatars as well.