SyncManager - More detailed info on startAll and syncAll

[ddenev]

I have read the documentation and all the examples, but I still cannot figure when to use startAll vs syncAll functions of SyncManager.

I know that startAll setups all collections to be synced w/ remote changes but I fail to understand in what scenarios should I use it compared to syncAll. I am very new to signaldb, so I apologize if my question sounds noob. I am writing my initialization code for my app and I wander - should I use startAll or syncAll after I create the SyncManager and add collections to it.

Can you please elaborate when to use each? Should I use them both at the same time when I am initializing my app? Some examples scenarios would be really helpful.

Thank you in advance!

[maxnowack]

Hi!
startAll registers remote change handlers and enables automatic pushing of changes made to items of the collection. syncAll on the other hand, pushes all changes manually and also does a pull. You should call startAll when you want to start syncing all your collections. Use syncAll to manually sync your collections 🙂

[maxnowack]

That's because the autostart parameter of the SyncManager defaults to true.

[ddenev]

aha! so, when the autostart option of SyncManager is true then I don't need to call startAll at all and startAll should only be used in cases when autostart was explicitly set to false, is that right?

[maxnowack]

Yes, that's right. Or in cases where you need to start the sync after manually pausing

[ddenev]

Thank you so much for explaining! 😊

[maxnowack]

You're welcome! 🙂