From 541257ccea31f9ef029092ef13e8de77462eea19 Mon Sep 17 00:00:00 2001
From: Xevion <xevion@xevion.dev>
Date: Tue, 24 Sep 2024 17:06:52 -0500
Subject: [PATCH] sync doc notes

---
 SYNC.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 SYNC.md

diff --git a/SYNC.md b/SYNC.md
new file mode 100644
index 0000000..84dcf64
--- /dev/null
+++ b/SYNC.md
@@ -0,0 +1,29 @@
+# sync
+
+Notes on the synchronization process by Todoist.
+
+## How do edited, completed, deleted, rescheduled and uncompleted items respond?
+
+Edited: Full object
+Completed: `is_completed`, full object
+Deleted: `is_deleted`, full object
+
+TODO: Rescheduled, uncompleted
+
+## How should synchronized items be identified/updated?
+
+The `id` detail.
+
+TODO: It is not well specified in the docs what the meaning of `v2_id` is.
+
+## What data structure should be used to store synchronized items?
+
+A dictionary with the `id` as the key.
+
+## How and when should synchronization be triggered?
+
+With the cron schedule, first thing.
+
+## Is there a limit to the delay between synchronization?
+
+Likely: if there is a limit, it should be handled automatically by the `full_sync` attribute.
\ No newline at end of file