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
Should we let people invoke setState in componentWillUnmount? It seems harmless, but currently we throw. In theory, this.state should be cleared out when unmounting (but we do not for backward compatibility reasons).
Aside, as we get better at clearing asynchronous callbacks on unmount, we should seriously consider clearing this.state and this.props when unmounting.
The text was updated successfully, but these errors were encountered:
Summary
===
1. Fix some errors manually
1. Copy some updated ContextMenu code from original React sources
Resolves#38.
Test Plan
===
1. `yarn flow`: No errors
1. `yarn lint`
1. `yarn test`
1. `yarn start`: Everything still works, especially the context menu.
Summary
===
1. Fix some errors manually
1. Copy some updated ContextMenu code from original React sources
Resolves#38.
Test Plan
===
1. `yarn flow`: No errors
1. `yarn lint`
1. `yarn test`
1. `yarn start`: Everything still works, especially the context menu.
Should we let people invoke
setState
incomponentWillUnmount
? It seems harmless, but currently we throw. In theory,this.state
should be cleared out when unmounting (but we do not for backward compatibility reasons).Aside, as we get better at clearing asynchronous callbacks on unmount, we should seriously consider clearing
this.state
andthis.props
when unmounting.The text was updated successfully, but these errors were encountered: