Jamie Adkins

I found that the time delta was very susceptible to high response times. We ended up using NTP servers based in our country and ignoring any delta that had a...

I can work around this particular issue by checking the network connection before calling `fetch`. e.g. ``` val activeNetwork = (CoreApplication.instance.getSystemService(Context.CONNECTIVITY_SERVICE) as ConnectivityManager).activeNetworkInfo val isConnected = activeNetwork != null &&...

Actually yeah you are right, it shouldn't happen. I didn't realise `concat()` waited for the first observable to complete. That makes this behaviour very strange. I'll put together a small...

@digitalbuddha I have a demo project for you to reproduce the bug. See [here](https://github.com/jamieadkins95/nytimes-demo). Strangely, I found that I got the expected behaviour (cached data and then onError) if I...

@digitalbuddha Hey, have you had a chance to take a look at this?

The issue is definitely caused by store.get() completing before the cached data has been completely propagated to the Observer. If you add a 100ms delay before you call store.fetch(), this...

Thanks for taking a look @brianPlummer! We have usecases where we would like the cached data and also the error so that we can show some data and then an...

> The onion diagram from Clean Arch always has the data layer as a superset of domain. By using that idea we would expect that when adding data as a...