Creating an "Instantfetch" React Router Link component about react-router-relay HOT 6 CLOSED

Also, @devknoll it'd be good to know if there is a bug for Relay not correctly detecting an in-flight query.

from react-router-relay.

Does this necessarily have to be a react-router-relay thing, though? Presumably a more generic solution is possible for any React Router based site (i.e. render the new whatever into an off-document div or something to handle all the data fetching).

I guess with Relay you have the concept of queries, but it'd be nice if we could find a generic solution that weren't restricted to just this one set of integrations.

from react-router-relay.

Oh interesting. I hadn't thought about making it generic. That would be really nice and work for more purposes other than just data fetching e.g. loading js chunks for new routes.

Is this possible though? I don't know React Router well enough to know you can load loading multiple routes at the same time.

from react-router-relay.

@KyleAMathews I was specifically referring to facebook/relay#140

from react-router-relay.

@KyleAMathews

The idea would be that you just load up the next location in an unmounted <div> somewhere, e.g. completely duplicate everything (but invisibly).

from react-router-relay.

I really feel like this would be best handled upstream in a more generic way in React Router. Most of the work here would be matching the route from link, then going from there. Please re-open this issue in some form on the React Router repo - it'd at least give us a better way to move forward on this, because I don't think I can handle this purely in react-router-relay.

from react-router-relay.