@ianlake The broad problem I have is that there appears to be no way for me to perform a local-only update that doesn't require a full refresh from the the network.
The concrete example in my situation is this: I fetch a list of news items from a remote API and map it into a domain type with fields sourced from a local database. On a database change, I would like to be able to patch in that updated item into the state maintained by Paging.
@msfjarvis mmm, but Paging itself doesn't care if the PagingSource you write is backed by a database directly (e.g., what the room-paging integration requires) or an amalgamation of two sources (web loaded content that isn't in a database + database content)?
A PagingSource load() can similarly do whatever you want based on the freshness of cached web content (i.e., not reload web content that is already up to date while always loading the latest local data) to form the final data to present.