From b6c0cf1820b464a4525d80356813f85d04b05290 Mon Sep 17 00:00:00 2001
From: Linus Rath <139418639+rathlinus@users.noreply.github.com>
Date: Thu, 29 Oct 2026 02:12:16 +0100
Subject: [PATCH] docs: say that Stalwart 1.0.0 answers the Metadata properties
 the calendar list leaves out

---
 src/api/calendar.ts | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/api/calendar.ts b/src/api/calendar.ts
index 2b174a14..1fcb97c6 100644
--- a/src/api/calendar.ts
+++ b/src/api/calendar.ts
@@ -420,10 +420,11 @@ export function resetSyntheticIdSupport(): void {
 }
 
 // The Calendar properties the app reads, which the default list on 0.16 and
-// 1.0 covers. Stalwart 1.0 advertises JMAP Metadata but its handlers are
-// still `todo!()`: a get that selects `metadata` or `privateMetadata` panics
-// on the server. An explicit list keeps them out even if a later release
-// adds them to the default. 0.16.6 knows every one of these.
+// 1.0 covers. The pre-releases of Stalwart 1.0 advertised JMAP Metadata with
+// handlers that were still `todo!()`: a get that selected `metadata` or
+// `privateMetadata` panicked on the server (1.0.0 answers it). An explicit
+// list keeps them, and whatever else a release adds to the default, out of
+// every calendar load. 0.16.6 knows every one of these.
 const CALENDAR_PROPERTIES = [
   'id', 'name', 'description', 'color', 'sortOrder', 'isSubscribed', 'isVisible', 'isDefault',
   'myRights', 'shareWith', 'defaultAlertsWithTime', 'defaultAlertsWithoutTime',