-
Notifications
You must be signed in to change notification settings - Fork 20
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
Wrong hooks order #9
Comments
Good point, although not sure what the ideal behaviour would be I unfortunately don't think it'd be possible to actually delay the Doing something like adding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let's say, we have two components (c1, c2) to replace with animation from c1 to c2.
Let's say we replace them in
out-in
mode.Then their hooks will be invoked in the following order:
componentDidMount
c2componentWillLeave
c1componentDidLeave
c1componentWillEnter
c2I put here only hooks that I use in my app, but it's enough to get the idea.
It can be easily got round by hiding c2 element's node in
componentDidMount
hook and showing back incomponentWillEnter
, but it's desirable to be fixed to make the solution solid.The text was updated successfully, but these errors were encountered: