Testing a Gemini codegen run

manual: module aliases

Changed files
+8 -9
output
+8 -9
output/jmap.mli
···
with a JMAP server.
Modules:
-
- {!Jmap_types}: Basic data types (Id, Date, etc.).
-
- {!Jmap_error}: Error types (ProblemDetails, MethodError, SetError).
-
- {!Jmap_wire}: Request and Response structures.
-
- {!Jmap_session}: Session object and discovery.
-
- {!Jmap_methods}: Standard method patterns (/get, /set, etc.) and Core/echo.
-
- {!Jmap_binary}: Binary data upload/download types.
-
- {!Jmap_push}: Push notification types (StateChange, PushSubscription).
-
- {!Jmap_email}: Mail extension (RFC 8621) types and methods.
-
- {!Jmap_unix}: Example interface for a Unix-based implementation.
+
- {!Jmap.Types}: Basic data types (Id, Date, etc.).
+
- {!Jmap.Error}: Error types (ProblemDetails, MethodError, SetError).
+
- {!Jmap.Wire}: Request and Response structures.
+
- {!Jmap.Session}: Session object and discovery.
+
- {!Jmap.Methods}: Standard method patterns (/get, /set, etc.) and Core/echo.
+
- {!Jmap.Binary}: Binary data upload/download types.
+
- {!Jmap.Push}: Push notification types (StateChange, PushSubscription).
+
- {!Jmap.Email}: Mail extension (RFC 8621) types and methods.
@see <https://www.rfc-editor.org/rfc/rfc8620.html> RFC 8620: Core JMAP
@see <https://www.rfc-editor.org/rfc/rfc8621.html> RFC 8621: JMAP for Mail