-
Notifications
You must be signed in to change notification settings - Fork 45.6k
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
Ordering of componentDidMount events #76
Comments
I can see why that would cause issues… The way you're thinking about sounds like common sense so I hope that's actually true and that we're just firing these callbacks in the wrong order. So I agree, but that's without looking at the code closely |
I think this makes sense. Here's my reasoning: One of the few valid reasons for wanting to use |
Currently, when mounting two nested components, componentDidMount fires on the outer element before the inner one:
http://jsfiddle.net/spicyj/udaq9/
I can't remember now why I was frustrated by this earlier in the week but I'd expect the inner component to be mounted completely before the outer component's componentDidMount method runs so that it can rely on the children being fully mounted.
Agree/disagree?
The text was updated successfully, but these errors were encountered: