Where/when to fetch data?

[ericflo]

In issue #38 it was suggested to discuss data fetching in another issue. I'll start:

Right now I've written my components such that the top-level components fetch data in a componentDidMount method. This is straighforward and works well for now, however, it won't work for server rendering, which the project I'm working on is going to need soon.

After already getting set up with react-nested-router, I came across RRouter, which has a fairly sane approach to this: http://andreypopp.github.io/rrouter/data-fetching.html It seems to me that this same approach could be applied to react-nested-router.

Thoughts?

[ryanflorence]

It's a good approach. I'd rather have the function on a static method of the handler, feels better to me than pulling in many fetch functions in the route config.

We will absolutely support this use case in one form or another soon.

Sent from my iPhone

On Jul 10, 2014, at 6:48 PM, Eric Florenzano notifications@github.com wrote:

In issue #38 it was suggested to discuss data fetching in another issue. I'll start:

Right now I've written my components such that the top-level components fetch data in a componentDidMount method. This is straighforward and works well for now, however, it won't work for server rendering, which the project I'm working on is going to need soon.

After already getting set up with react-nested-router, I came across RRouter, which has a fairly sane approach to this: http://andreypopp.github.io/rrouter/data-fetching.html It seems to me that this same approach could be applied to react-nested-router.

Thoughts?

—
Reply to this email directly or view it on GitHub.

[mjackson]

@ericflo We're discussing server-side rendering on #57. It's definitely a use case we will support.

[mjackson]

Let's continue this discussion in #57.