From f64eec5a93779e1cbdaad87c39595fecab2c4697 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= <76261501+zecakeh@users.noreply.github.com> Date: Thu, 28 Nov 2024 15:49:35 +0100 Subject: [PATCH] Use `json` instead of `json5` for syntax highlighting (#2017) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Use json instead of json5 for syntax highlighting Chroma, the library used for syntax highlighting in Hugo, does not support JSON5 so those code blocks were not highlighted. However it supports comments in JSON so they are highlighted correctly in the rendered spec. Signed-off-by: Kévin Commaille * Add changelog Signed-off-by: Kévin Commaille --------- Signed-off-by: Kévin Commaille --- changelogs/client_server/newsfragments/2017.clarification | 1 + content/client-server-api/modules/event_replacements.md | 4 ++-- content/client-server-api/modules/rich_replies.md | 4 ++-- 3 files changed, 5 insertions(+), 4 deletions(-) create mode 100644 changelogs/client_server/newsfragments/2017.clarification diff --git a/changelogs/client_server/newsfragments/2017.clarification b/changelogs/client_server/newsfragments/2017.clarification new file mode 100644 index 000000000..a202eec32 --- /dev/null +++ b/changelogs/client_server/newsfragments/2017.clarification @@ -0,0 +1 @@ +Use `json` instead of `json5` for syntax highlighting. diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md index 50109d073..11e755de0 100644 --- a/content/client-server-api/modules/event_replacements.md +++ b/content/client-server-api/modules/event_replacements.md @@ -309,7 +309,7 @@ for re-notifying if the sending client feels a large enough revision was made). For example, if there is an event mentioning Alice: -```json5 +```json { "event_id": "$original_event", "type": "m.room.message", @@ -324,7 +324,7 @@ For example, if there is an event mentioning Alice: And an edit to also mention Bob: -```json5 +```json { "content": { "body": "* Hello Alice & Bob!", diff --git a/content/client-server-api/modules/rich_replies.md b/content/client-server-api/modules/rich_replies.md index ef07b6972..6445dc4bb 100644 --- a/content/client-server-api/modules/rich_replies.md +++ b/content/client-server-api/modules/rich_replies.md @@ -31,7 +31,7 @@ the `rel_type` and `event_id` properties of `m.relates_to` become *optional*. An example reply would be: -```json5 +```json { "content": { "m.relates_to": { @@ -187,7 +187,7 @@ of the replied to event and any users mentioned in that event. See An example including mentioning the original sender and other users: -```json5 +```json { "content": { "m.relates_to": {