-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Transition and promises #2098
Comments
I'm sorry. I don't understand your question. |
Hups, sorry for that. I guess #2101 explains it better ("This is simple if you don't care about transitioning") |
@bbnnt you could just adapt my middleware component — that you referenced — for your use. It would enable you to use There is no built-in way — that I can see — of doing this. |
is this still an issue @bbnnt ? if yes than I'll reopen |
@knowbody here (https://github.com/rackt/react-router-mega-demo/blob/master/app/handlers/Root.js#L61) it handles the "component" load |
Well, the point here will be based on the use of react-resolver; but maybe this problem could affect a larger audience. What react resolver does, is that it wait for the data before rendering. Forget bout transitioning components then when using react-router.
I've looked into many issues here that could relate, but I can't get a real understanding of the state of this problem. Can react-router wait for the component to render and still manage a regular css transition ?
The text was updated successfully, but these errors were encountered: