nextcloud / nextcloud/calendar
Import: check if UID already exists, check which one is newest and update if necessary.
Open
Nobody has claimed this yet.
1. to develop
enhancement
Feature: Importing
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
- Before importing, send request with all UIDs to the server. (or maybe not all but 50 at a time)
- If it doesn't give a 404, parse the calendar-data from the server and compare the LAST-MODIFIED and SEQUENCE-properties of both.
- If the version, the user wishes to import, is newer, update the event on the server.
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
No files or tests are named. Start by tracing the JavaScript import flow and its CalDAV requests; determine how existing UIDs, calendar-data, LAST-MODIFIED, and SEQUENCE are retrieved and compared. Done means newer imported events update the server while older ones do not, including the chosen request batching behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100