Jesse Niininen
Jesse Niininen
Could you give some example use case? In what case would you need multiple queries instead of using fragments to make them into one query? Using multiple queries for a...
> We can't do it using one query as we can't cache query parts in Relay. You can cache query parts if you want and relay will only fetch the...
Hey you're absolutely correct, I had the wrong impression of how relay uses the cache! I now see the use case for this and might use this myself if it...
Personally I think it would be more clean to add new prop `preloadedQueries` which includes all queries (including the first one) in array. `preloadedQuery` could be kept just for backwards...
Was just thinking about this and realized this would also solve the underlying issue in #73. Or at least be a workaround for it.
> especially for ServerSide/Isomorphic Suspense :-) I'd just like to point out that you can use `Suspense` server side without concurrent features. Doesn't really help if you want to use...
There seems to be something more weird going on with undefined values, they're not really sorted properly at all. See repro: https://codesandbox.io/s/exciting-shape-5xgj1q?file=/src/main.tsx:573-592  Or when the column...
Well gotta say that this "easy" task is harder than most hard challenges 😄
We have utility function we use to add the withRelay, translations etc, but even when I reduced it to this: ```ts export default withRelay(HomePage, IndexQuery, { createClientEnvironment: () => getClientEnvironment()!,...
Okay I finally found the problem. pageProps has `preloadedQuery` field which is not enumerable meaning that it's lost when we do `{...pageProps}` in one of our _app.tsx wrapper components. This...