-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Improve support for server rendering async routes #2883
Conversation
import Link from '../Link' | ||
import match from '../match' | ||
import RoutingContext from '../RoutingContext' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wasn't actually testing the v1 API. Now it is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!
LGTM. |
We initially discussed not doing this in #2036 (comment) and subsequently, but I think this is lightweight enough, and it solves the "async What do you think? |
Improve support for server rendering async routes
👍 |
} | ||
// Use initial state from renderProps when available, to allow using match | ||
// on client side when doing server-side rendering. | ||
const { location, routes, params, components } = this.props |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this! I just got async routes working with RC4, had some issues, but you fixed it for me :)
👍 @taion
Closes #2714