Open untitaker opened 8 years ago
From what I can tell:
Might raise issues due to bugs in collective/icalendar Code migration cost Bugfixes might be tied to collective/icalendar releases
Will help find bugs in collective/icalendar Reduced maintenance cost Will probably raise awareness of issues we haven't found yet Maybe we can detect earlier if we're sending invalid events to a server?
Maybe we can detect earlier if we're sending invalid events to a server?
Interesting idea, but I'm unsure about this, as a "generic" implementation would also prevent downloading broken events from a server. Perhaps put it into the repair
command.
Alternatively use https://github.com/eventable/vobject, which seems to be Py3 compatible and also can parse both iCalendar and Vobject
Quick note: In #428 we figured out that vobject has many bugs. We do need absolutely correct serialization/deserialization roundtrip because of the singlefile/http storages.
I think we should use vobject anyway. I wonder if there's a good set of weird vcards somewhere, to test with vobject.
Our current sloppy parser is not exactly a maintenance burden, but it's annoying to have it here in the first place.
Two things need to be resolved for this:
I'm unsure if this is worth it, given how well the sloppy parser in
vdirsyncer.utils.vobject
has worked in the past.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.