-
-
Notifications
You must be signed in to change notification settings - Fork 319
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
Missing componentDidCatch #17
Comments
And also getDerivedStateFromError will be available in v 16.6. |
Both are available now, any chance of getting the diagram updated? |
Both |
@wojtekmaj Actually I think they does belong to 'less common lifecycles'. IMO one of the goals of this diagram is to help people understand the execution sequence of lifecycle methods. At some point, we would wonder when componentDidCatch and getDerivedStateFromError are executed. |
Hopefully, we wonder first, then implement. ;) |
No description provided.
The text was updated successfully, but these errors were encountered: