I wanted some advice on how to wire up Apollo Exe

Question

< mbonnin> I wanted some advice on how to wire up Apollo ExecutionContext and use them internally

yschimke · Answer

Context is <https github com joreilly Confetti pull 1001>

yschimke · Answer

Basically I want to ensure we do the right things on Wear based on the request and network types

yschimke · Answer

So make images optional Coil or only perform an API request if it s the first request not a refresh or we have Bluetooth connection

yschimke · Answer

I don t think I can do this currently with Apollo

yschimke · Answer

I have all the OkHttp plumbing in place to choose the right network and whether to fail it immediately

yschimke · Answer

But I need to choose an approach for Apollo

yschimke · Answer

1 Just avoid making the call based on the network and cache state and hope it will use the network This unfortunately muddies up the app code and probably means this code on Wear differs from mobile

yschimke · Answer

2 Find out how to get some indication of the Cache status or current Fetch policy at the OkHttp layer Seems too much logic needs to be built into Apollo

yschimke · Answer

3 Have a way to pass ExecutionContext through to OkHttp Request Then set this when making the call

mbonnin · Answer

Indeed the `ExecutionContext` isn t passed to the `HttpEngine` We ve had this issue previously and workarounded with HTTP headers that we would filter out before sending them

yschimke · Answer

Good idea

mbonnin · Answer

Let me know how that works I ll also tinker with passing the `ExecutionContext` all the way through that might come in handy

yschimke · Answer

The aim is to express the difference between user clicking login or bookmark which should wake up network

yschimke · Answer

And optimistically refreshing cached content just in case which shouldnt

mbonnin · Answer

What if refreshing cached content and that reaches OkHttp That would be an error right

mbonnin · Answer

I guess I m still trying to figure out what s wrong with your 1 solution above

yschimke · Answer

Network situation may change in between

mbonnin · Answer

I think I got it Login = gt Bookmarks = gt NetworkOnly Refreshing Cache Content = gt CacheAndNetwork but not wake up network

yschimke · Answer

I d like a solution that can guarantee a setting like use LTE

yschimke · Answer

Yep

mbonnin · Answer

Makes sense +1

yschimke · Answer

Does the cache status get computer anywhere Or I should split the CacheAndNetwork into separate calls

mbonnin · Answer

You mean is the network call aware of a previous cache attempt and whether it s a cache hit I don t think that s the case

mbonnin · Answer

gt I ll also tinker with passing the `ExecutionContext` all the way through This is what I came up with Let me know what you think <https github com apollographql apollo kotlin pull 5383>

yschimke · Answer

Yeah I think so Would need to try Is there an alpha phase where it s usable but not fixed permanently

mbonnin · Answer

It s published to SNAPSHOTs after the merge

yschimke · Answer

API wise I guess I d wonder about extending Vs some extension point where the default is an identity impl

yschimke · Answer

But that s your call This looks like what I need

mbonnin · Answer

I contemplated `DefaultHttpEngine callFactory configure apollographql Request okhttp3 Request Builder gt Unit ` for a while but was a bit afraid this would be limited and felt a bit out of place

mbonnin · Answer

I ll merge so you can try the SNAPSHOTs The whole v4 is still beta as well so we can still change things

yschimke · Answer

nit Once the snapshot is available it should resolve itself But copying code it appears UploadsHttpBody is ApolloInternal

yschimke · Answer

This deploy failed will grab the next one <https github com apollographql apollo kotlin actions runs 6936908864>

mbonnin · Answer

I ve relaunched the deploy it <https github com apollographql apollo kotlin actions runs 6936908864|worked> this time Re UploadsHttpBody I d rather keep it ApolloInternal for now GraphQL uploads have never been specified and have possible security issues so they ll probably become deprecated at some point