Add some docs for app.store.update if data changed in mean time

[hoodiehq]

Add some docs for app.store.update if data changed in mean time

[gr2m]

Thanks for raising the question – and sorry for the late response!

this is how it's working at the moment: your local changes get always pushed, possible conflicts remain in the couch and may be resolved, or just left. Changes coming from remote do always overwrite your local data at the moment, there is no check if your data changed locally meanwhile, we probably should add such a thing.

What would be your desired behavior / API?

[jviereck]

What would be your desired behavior / API?

Maybe have a way to specify a callback onConflict, that is called once a conflict is detected. The developer can then implement some functionality to resolve the conflict. If the callback is not specified, the default CouchDB way of handling/merging is used.

Sorry, I still haven't looked too much into how conflict resolving works in CouchDB, so I can only give that high-level API-idea response :/

[gr2m]

We have the concept of modular background workers acting on changes in the databases.

What we could do is to implement a "conflict resolution worker". In the admin backend of your app, you could define a JavaScript function that gets called each time there is a conflict and that contains the custom logic to resolve the conflict.

Makes sense?

[jviereck]

+1

[gr2m]

I've created a new repo for a worker that will resolve conflicts in the backend:
https://github.com/hoodiehq/worker-conflict-resolver