Consider updating the docs for isLast on ApolloResponse if they are not up to date about apollo-kotlin HOT 13 OPEN

Thanks! I've removed the example about CacheAndNetwork here.

I've left the caveat about false negatives for now - I'm a bit reluctant to remove it since it still makes sense that some producers may not have a way to know when an item is the last one, even if I can't think of specific examples of that.

from apollo-kotlin.

That's great, thanks for addressing this!

When we mention that some producers may not know when the item is the last one, is that for other interceptors that users of this library may be creating themselves, or something that even if you can't think of a real example, may still potentiall happen using any of the CacheFirst, CacheOnly, NetworkOnly, NetworkFirst and CacheAndNetwork fetch policies?

from apollo-kotlin.

User defined interceptors is certainly a case. This should never happen due to the regular fetch policies.

I was also thinking of something like @defer where the backend emits several items - in that instance we actually do know when an item is the last, but I'm imagining maybe future GraphQL features won't be able to guarantee it.

from apollo-kotlin.