Name vcf-files by UID? label:question about ppl HOT 9 CLOSED

the names of the vcf files don't matter at all. It's just that vdirsyncer uses either a UID or a hash for the filename when creating new items, renaming them with mv or ppl is tolerated by vdirsyncer.

from ppl.

There is nothing stopping you from using ppl with vdirsyncer. You just have to commit manually to the contacts repository after each vdirsyncer sync (which can be automated though), so ppl recognizes the changes. So this is working in the bigger sense.

An issue i encountered though: If i edit a contact in any way, ppl discards any unknown fields (such as a contact picture) when renaming the file.

from ppl.

Yo @untitaker, thanks for finding a way of making vdirsyncer and ppl play nice together in their current forms. I'm really reluctant to change the directory structure or file naming convention if I can avoid it. I consider it part of ppl's public API.

That issue about discarding unknown fields sounds like a real pain. Not sure how fixable it is, but I'll have a think. Sorry it took me so long to actually acknowledge this question by the way.

from ppl.

Hey @hnrysmth any update on this?

from ppl.

I'm not at all familiar with Ruby, but I think it is a good solution to store the GreenCard::Vcard object on the Contact instance, and re-use it when encoding. While that would create a "dirty" attribute for the Contact class, it still avoids making the code more vcard-specific than other solutions.

from ppl.

Any update?

from ppl.

Hey @untitaker I know I've been a crappy maintainer this year. If you're still interested in working on this I'll be more than happy to add you as a proper collaborator to the project so that you don't have to worry about your work sitting unused because of me 😳

from ppl.

I'm not particularly interested atm but I've hit a problem while working on #52. See comments there.

from ppl.

Gonna close this issue actually.

from ppl.