From d1b4c72762c4ba0da05c9408c9eba52295a448d3 Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 17 May 2023 14:53:24 +0100 Subject: [PATCH] Failure to YAML --- data/event-schemas/schema/m.call.reject.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/event-schemas/schema/m.call.reject.yaml b/data/event-schemas/schema/m.call.reject.yaml index ee4d0b1d..6793219c 100644 --- a/data/event-schemas/schema/m.call.reject.yaml +++ b/data/event-schemas/schema/m.call.reject.yaml @@ -11,8 +11,8 @@ description: | the callee sends an `m.call.hangup` event. If the calling user chooses to end the call before setup is complete, the client sends `m.call.hangup` as previously. -Note that, unlike `m.call.hangup`, this event has no `reason` field: the rejection of -a call is always implicitly because the user chose not to answer it. + Note that, unlike `m.call.hangup`, this event has no `reason` field: the rejection of + a call is always implicitly because the user chose not to answer it. allOf: - "$ref": core-event-schema/room_event.yaml properties: