Jimmy Jia

Interesting – I guess we need to fix the type definition to treat the default `as` as `a` rather than `button` when `href` is specified. We'd be happy to take...

To get by for now, I'm using this code: https://github.com/taion/relay-todomvc/blob/found-modern-universal/src/fetcher.js Essentially a one-time use response cache, that uses the order of the requests (which for these purposes will be deterministic)...

I think something like what I have for my Relay-TodoMVC example is basically correct. It just needs to be hardened to deal with errors and such. Just checking if there's...

You should follow the pattern in https://github.com/4Catalyzer/found-relay/blob/master/examples/todomvc-modern-universal/src/fetcher.js for now. Note the caching is at the level of the network requests, not the Relay data.

The `ClientFetcher` takes advantage of how requests go out in the same order. It takes the initial responses from the server, and just returns those as the responses for the...

As in the fetcher handles the caching... so really it's your network layer that's handling it, and it only knows about requests, not about the schema per se.

See https://github.com/4Catalyzer/found-relay/tree/master/examples/todomvc-modern-universal.

Hydration is to get the site working again on the client. For pure SSR, it’s just the markup you care about. You hydrate to pick things up on the client,...

That's not a very good implementation... you're not caching the response results at all, so in fact you block on the client-side render until the initial fetch succeeds. Hydrating the...

Yes – that's exactly what I do in https://github.com/4Catalyzer/found-relay/blob/v0.3.0-alpha.9/examples/todomvc-modern-universal/src/server.js#L79 (though `serialize-javascript` per that example is a better option than the Yahoo serialize library, which adds a lot more overhead than...