From db302b66ca5e6394aeb7d404233b0389b2eef5bf Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Sat, 1 Sep 2018 02:44:53 +0100 Subject: [PATCH] revert example which was corect first time; fix rst --- .../event-schemas/m.direct_to_device.yaml | 17 ++++++++--------- specification/server_server_api.rst | 2 +- 2 files changed, 9 insertions(+), 10 deletions(-) diff --git a/api/server-server/definitions/event-schemas/m.direct_to_device.yaml b/api/server-server/definitions/event-schemas/m.direct_to_device.yaml index b151158a8..48cdc4ed7 100644 --- a/api/server-server/definitions/event-schemas/m.direct_to_device.yaml +++ b/api/server-server/definitions/event-schemas/m.direct_to_device.yaml @@ -51,17 +51,16 @@ allOf: The contents of the messages to be sent. These are arranged in a map of user IDs to a map of device IDs to message bodies. The device ID may also be *, meaning all known devices for the user. - example: |- - { - "alice@example.org": { - "IWHQUZUIAH": { - "algorithm": "m.megolm.v1.aes-sha2", - "room_id": "!Cuyf34gef24t:localhost", - "session_id": "X3lUlvLELLYxeTx4yOVu6UDpasGEVO0Jbu+QFnm0cKQ", - "session_key": "AgAAAADxKHa9uFxcXzwYoNueL5Xqi69IkD4sni8LlfJL7qNBEY..." - } + example: { + "alice@example.org": { + "IWHQUZUIAH": { + "algorithm": "m.megolm.v1.aes-sha2", + "room_id": "!Cuyf34gef24t:localhost", + "session_id": "X3lUlvLELLYxeTx4yOVu6UDpasGEVO0Jbu+QFnm0cKQ", + "session_key": "AgAAAADxKHa9uFxcXzwYoNueL5Xqi69IkD4sni8LlfJL7qNBEY..." } } + } required: - sender - type diff --git a/specification/server_server_api.rst b/specification/server_server_api.rst index 9f11ce9c9..80da7c958 100644 --- a/specification/server_server_api.rst +++ b/specification/server_server_api.rst @@ -1018,7 +1018,7 @@ The server API for send-to-device messaging is based on the following EDU. There are no PDUs or Federation Queries involved. Each send-to-device message should be sent to the destination server using -the following EDU:: +the following EDU: {{definition_ss_event_schemas_m_direct_to_device}}