IssueTracker

We are potentially adding some new APIs to accept CoroutineContext in https://android-review.googlesource.com/c/platform/frameworks/support/+/2065409.

If a user passes a Job into the CoroutineContext, they may unexpectedly prevent cancellation on collection of a PagingData from the library. while this should not affect future emissions of PagingData - we should still investigate whether this has any impact on the common use cases of Paging.

In particular - does this make .collectLatest a requirement or does it prevent collector from observing new generations entirely?

We can mitigate this potential footgun by catching custom Job passed to the contexts, but we should first make sure this is actually a problem as it is possible that it could be desirable for user to control this.