pimutils / pimutils/vdirsyncer
Use external library for vobject parsing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 185
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 1
Description
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:
- vcard support as discussed in https://github.com/collective/icalendar/issues/186 -- we absolutely need some sort of support because of #89, #70, etc
- lazy parsing, see https://github.com/collective/icalendar/issues/158 -- eager parsing as of right now is IMO quite slow, and not appropriate given how few operations vdirsyncer actually does on item contents.
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading vdirsyncer.utils.vobject and the linked discussions for vcard support and lazy parsing. Compare external-library options against the required vcard support and deferred parsing behavior; done means the current parser is replaced without losing the needed item-content operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100