Skip to content
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

Closed
adamscybot opened this issue Dec 17, 2015 · 4 comments
Closed

Purpose and motivation? #13

adamscybot opened this issue Dec 17, 2015 · 4 comments

Comments

@adamscybot
Copy link

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.

@ryanflorence
Copy link
Owner

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.

@ryanflorence
Copy link
Owner

heh, the readme really said nothing at all, did it?

21070c1

Thanks.

@adamscybot
Copy link
Author

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

@ryanflorence
Copy link
Owner

Yeah, though I think of it less as a competitor and more of a reference implementation for those libs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants