matt-dalton

Hi @henrikbjorn ...I am also struggling with this problem. Did you find a solution in the end?

I'm also having problems here. With a `DjangoConnectionField` it is at least possible to work round this by creating your own NonNullConnection class, but I can't find such a solution...

Also struggling with this. The solution above looks pretty decent, thanks @boolangery , although I'm slightly nervous it will lead to edge cases down-the-line. Seems weird that there's not some...

Although I've just tested it and it seems to not work for me...very similar setup to you. Does this query output the same IDs for `users` and `publicUsers` @boolangery ?...

> But there is a relative advantage here: since the developers do this every time, they control what exactly was updated in the folder. And if many new dependencies were...

I'd just imagine that if you try and run your app using a node server without a proper mobile native build environment, something would crash?

Ahh gotcha. Does that mean there is no way to default to loading these values from the cache? And you can only use `withQueryRenderer` results offline?

Interesting. I've been playing about with this, and see that you can write something like ``` import { createOperationDescriptor, getRequest } from 'relay-runtime' const operation = createOperationDescriptor(getRequest(query)) data = await...

I'd like to be able to do exactly that - recreate the use-cache-if-offline functionality from the query renderer but using the imperative `fetchQuery`. Is there a reason why this is...

> I'm curious about how you're using the library / offline to see if there's anything to improve in react-relay-offline or recommend other solutions. _Our use case:_ We have one...