Show HN: React Resolver – Async Rendering and Data-Fetching for React

Re:Show HN: React Resolver – Async Rendering and Data-Fetchi... by mike-cardwell on Monday August 10, 2015 @07:29AM (#10033859)

Seems incompatible to me. You don't fetch data inside the components when you're using Flux.

[ Parent | on HN ]

Re:Show HN: React Resolver – Async Rendering and Data-Fetchi... by ericclemmons on Monday August 10, 2015 @10:40AM (#10034888)

It's compatible, as this is live in production today with a Flux library, and there are Alt & Redux examples in the works.

How you choose to fetch data is up to you, whether you use Flux, or fire AJAX calls within the `@resolve` function.

That's your code, not mine. I just make it so you can put your data requirements _beside_ your component instead of several layers up :)

[ Parent | on HN ]

Re:Show HN: React Resolver – Async Rendering and Data-Fetchi... by idibidiart on Monday August 10, 2015 @10:35AM (#10034844)

but isn't the plan with Relay to do just that? or not?

[ Parent | on HN ]

Re:Show HN: React Resolver – Async Rendering and Data-Fetchi... by ericclemmons on Monday August 10, 2015 @10:44AM (#10034925)

You're correct in that Relay correctly identified the same architectural problem with having data requirements _far away_ from the components that actually need it.

This is why React Resolver was created, and from what I've seen, also spurred React Nexus & React Transmit as well.

On an related note, v1 of React Resolver explicitly stated how it was similar to Relay with regards to fetching data for components. I've since dropped that messaging to avoid confusion since Relay isn't even available yet :)

[ Parent | on HN ]