From 7cc6d6e3598a3e59264ae737d6f9337935264d9a Mon Sep 17 00:00:00 2001
From: Andrew Morgan <andrew@amorgan.xyz>
Date: Fri, 4 Aug 2023 10:25:52 +0100
Subject: [PATCH] fix up the 404 response schema

it wasn't displaying correctly in the rendered spec otherwise
---
 data/api/client-server/report_content.yaml | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/data/api/client-server/report_content.yaml b/data/api/client-server/report_content.yaml
index 21b201c9..53526460 100644
--- a/data/api/client-server/report_content.yaml
+++ b/data/api/client-server/report_content.yaml
@@ -79,18 +79,23 @@ paths:
               examples:
                 response:
                   value: {}
-        404:
+        "404":
           description: |-
             The event was not found or you are not joined to the room where the
             event resides.
             
             Homeserver implementations can additionally return this error if the
             reported event has been redacted.
-          examples:
-            application/json: {
-              "errcode": "M_NOT_FOUND",
-              "error": "The event was not found or you are not joined to the room."
-            }
+          content:
+            application/json:
+              schema:
+                $ref: definitions/errors/error.yaml
+              examples:
+                response:
+                  value: {
+                    "errcode": "M_NOT_FOUND",
+                    "error": "The event was not found or you are not joined to the room."
+                  }
           schema:
             $ref: "../client-server/definitions/errors/error.yaml"
       tags: