Trigger sync about synckit HOT 1 OPEN

Hey @teawithfruit, generally you want to create one synchronizer per model, so if you're using Core Data you would have one synchronizer for your managed object context, and if you're using Realm you would have one synchronizer for your entire realm.

I would recommend creating your synchronizer once (I use the AppDelegate in the example), then pass it to each controller that needs it using dependency injection (here), so they can trigger synchronisation.

In another app of my own I use a protocol like this

protocol SynchronizationInteractor: AnyObject {
    var isSynchronizationEnabled: Bool { get }
    var isSynchronizing: Bool { get }
    var error: Error? { get }
    func synchronize(completion: ((Error?) -> ())?)
    func cancel()
}

And then implement it in a class that owns the synchronizer but doesn't expose it. So the rest of the app is fully agnostic to the technology that's being used to synchronize data.

In the case of the example app it uses VIPER and sets up all dependencies in the App Delegate, but I could give more specific advice depending on how you're architecting your app.

from synckit.