-
Notifications
You must be signed in to change notification settings - Fork 48
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
Purpose and motivation? #13
Comments
Server and client. Point is to load data while the old screen is rendered, then transition to the new page once data has loaded. As soon as the code works as its supposed to, then we'll spend some time on docs. |
heh, the readme really said nothing at all, did it? Thanks. |
Thanks, that helps a lot. In a way, I guess this is a (much simpler) competitor of https://github.com/RickWong/react-transmit and https://github.com/ericclemmons/react-resolver |
Yeah, though I think of it less as a competitor and more of a reference implementation for those libs. |
I feel like the readme of this repo needs an explanation for the motivation behind this library.
As far as I can see, the main purpose is providing a known interface that a server can use to know when a route has all of its asynchronous resources loaded that are required for a full render. I hope I'm correct here, but I only discovered this after reading into server side react for the first time.
The text was updated successfully, but these errors were encountered: