At present, fetcher emissions are locked until reader emits, in order to preserve emission order. This presents a problem in the case that you do not want to emit from reader for a given condition, but instead return an emptyFlow. In this case, fetcher will never emit because reader never emits.
A potential solution would be to add some sort of "disk required" property to StoreRequest in order to either enforce current the fetcher lock behavior or skip the reader emission in the case that fetcher emits first.
To work around this, I have moved the conditional logic in fetcher to a map on stream(). However, it would be ideal to instead provide this behavior as part of the library.
Here's an example of the above:
sealed class GetItemError {
data class Missing(val itemId: ItemId): GetItemError()
data class Failure(val error: Exception): GetItemError()
}
typealias GetItemResult = Either<GetItemError, Item>
typealias GetItem = (ItemId) -> Flow<GetItemResult>
val fetcher: GetItem =
{ itemId ->
try {
val item = itemApiService.getItemById(itemId)
if (item != null) {
flowOf(Right(item))
} else {
flowOf(Left(GetItemError.Missing(itemId)))
}
} catch(e: Exception) {
flowOf(Left(GetItemError.Failure(e)))
}
}
val reader: GetItem =
{ itemId ->
val item = itemDao.getItemById(itemId)
if (item != null) {
flowOf(Right(item))
} else {
// Return empty Flow instead of `GetItemError.Missing` because DB
// isn't populated yet and this is not an error case.
emptyFlow()
}
}
At present,
fetcheremissions are locked untilreaderemits, in order to preserve emission order. This presents a problem in the case that you do not want to emit fromreaderfor a given condition, but instead return anemptyFlow. In this case,fetcherwill never emit becausereadernever emits.A potential solution would be to add some sort of "disk required" property to
StoreRequestin order to either enforce current thefetcherlock behavior or skip thereaderemission in the case thatfetcheremits first.To work around this, I have moved the conditional logic in
fetcherto amaponstream(). However, it would be ideal to instead provide this behavior as part of the library.Here's an example of the above: