eight

> Create the same styles that where synced previously When you create a style, it is not the same style in your cloud. > * Import When importing styles, I...

> I don't know how to remove the dupes without doing manually going one by one. I still suggest deleting them manually because clearing the database won't clear your cloud....

> detect the local styles before pulling to check if they are already present? It does but the sync manager uses an ID to identify a style. This allows you...

> same sourceCode or the same sections code, we should either automatically assume it's the same This will prevent us from duplicating styles. > change the local style's sync id...

I suggest the simpler, the better. For users, just don't import the same source code multiple times, or they will have multiple styles. Note that importing to each of three...

How would it handle duplicated styles on the cloud or styles both on the cloud and local?

> Normally there are no duplicates in the cloud and no duplicates locally In this issue, they are both in the cloud and local machines. If it is for common...

Here is a small demonstration of how this kind of automatic deletion may lead to data loss: Suppose A has `File(a)`, B has `File(b)`. The boss told them when they...

> Its _rev is not present in the cloud. Can you elaborate? `_rev` is a tag locally set by the client. Two documents will have different `_rev`. Two versions of...

If the cloud supports HEAD requests, it should be possible to request the cloud and ask for the existence. However, if there was an incomplete sync, there might be staled...