From ecd0db5a7a998492aa2ca64cbeee4cd3f3702d01 Mon Sep 17 00:00:00 2001
From: Christoph Wurst <christoph@winzerhof-wurst.at>
Date: Wed, 10 Nov 2021 10:46:40 +0100
Subject: [PATCH] Document calendar write API for app devs

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
---
 .../digging_deeper/groupware/calendar.rst     | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/developer_manual/digging_deeper/groupware/calendar.rst b/developer_manual/digging_deeper/groupware/calendar.rst
index 84e858219..f8d22d997 100644
--- a/developer_manual/digging_deeper/groupware/calendar.rst
+++ b/developer_manual/digging_deeper/groupware/calendar.rst
@@ -37,6 +37,28 @@ To provide calendar(s) you have to write a class that implements the ``ICalendar
 
 This ``CalendarProvider`` class is then registered in the :ref:`register method of your Application class<Bootstrapping>` with ``$context->registerCalendarProvider(CalendarProvider::class);``.
 
+
+Write support
+~~~~~~~~~~~~~
+
+Calendars that only return `ICalendar` are implicitly read-only. If your app's calendars can be written to, you may implement the ``ICreateFromString``. It will allow other apps to write calendar objects to the calendar by passing the raw iCalendar data as string.
+
+.. code-block:: php
+
+    <?php
+
+    use OCP\Calendar\ICreateFromString;
+
+    class CalendarReadWrite implements ICreateFromString {
+
+        // ... other methods from ICalendar still have to be implemented ...
+
+        public function createFromString(string $name, string $calendarData): void {
+            // Write data to your calendar representation
+        }
+
+    }
+
 Resources
 ---------