Handle Google Calendar revisions/updates gracefully
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Whenever someone changes an event on Google Calendar, I get an email for the update. As usually with new invites, I run khal import on the new ics file. However, it doesn't work as expected since Google Calendars sends a special "revision" ics file, and not just the updated ics file with the same UID.
For example,
Original: UID:4c5755og4bqqlj9inge3xxxxxx@google.com
New: UID:4c5755og4bqqlj9inge3xxxxxx_RyyyymmddThhmmss@google.com
In this case, since the UID is not the same, khal fails to catch this case and creates a fresh new event instead of updating. This situation should instead be handled gracefully.
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 tracing the khal import handling for incoming ICS files and how event UIDs are matched. Use the Google Calendar examples in the issue to understand the revision UID pattern. Done means importing a revision updates the existing event instead of creating a duplicate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100