Peter Livesey

Oh, if you want to add an extension as a workaround, it'd be easiest to depend on master instead of the latest. On Mon, Jan 23, 2017 at 8:53 AM...

That seems like a great workaround for now. I'll add the other API soon. On Mon, Jan 23, 2017 at 4:07 PM Mark Krenek wrote: > You're talking about listenToModelIdentifier...

Hmmmm...so I looked into this more, and it's a bit more complicated than I thought. After adding this feature, a bunch of tests started failing. The shared collection stuff gets...

No progress...sorry, been busy with a new job. I may have some time to look over the weekend. The main problem is, I'm afraid of doing this in a general...

If you use the same `cacheKey`, you'd end up overwriting your old versions of the data in the cache (and other data providers). I assume this isn't what you want....

Sorry for the slow response. Just catching up but yes, a PR would be welcome. Thanks! On Thu, Jan 19, 2017 at 5:22 PM Mitchell Porter wrote: > Just cloned...

I don't know of specific apps, but you can try PMing some of the people who've opened issues to see what apps they are working on.

Hmmm...looks like this may already be possible with data providers. It looks like you can create a `DataProvider` and set `modelIdentifier`. Then, once the model is available, it'll be set...

Sorry for the slow response, but a few things to check: 1. Put a break point in your cache delegate in: `func modelForKey(_ cacheKey: String?, context: Any?, completion: @escaping (T?,...

In the LinkedIn app, when the user logs out we tear down all the view controllers. Since the data providers are owned by the view controller, they automatically get purged....