Open jacobmarble opened 7 years ago
I'm in the middle of refactoring the related code (vdirsyncer already ignores changes that just reorder properties, e.g.), ignoring case of property names is totally a good idea that can be done by default.
Ah, you want the normalized variant in the diff as well! This can actually be solved as part of https://github.com/pimutils/vdirsyncer/issues/375
I edited my original comment.
This feature request is about merging a vcard that changed on both sides, but in non-conflicting ways. In my example, side A changed the name, while side B added an org. Some normalization would certainly be required to implement.
I see. That merging strategy, however, requires that vdirsyncer stores the entire item content inside the status (to figure out which properties changed) instead of just a hash. And it is blocked by #375 as well.
Just getting started with vdirsyncer, starting with contacts. One of my first tests is a vcard like this:
Change on side A (modify name):
Change on side B (add org):
As expected, this error is returned:
However, the changes themselves do not conflict. What I would like is to see both sides change to:
Is it worth my time to implement a diff checking whether changes can be resolved without forcing one side to simply override the other? Looks like this could be implemented with
["command", "my_command"]
.