Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use json instead of json5 for syntax highlighting #2017

Merged
merged 2 commits into from
Nov 28, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Use `json` instead of `json5` for syntax highlighting.
4 changes: 2 additions & 2 deletions content/client-server-api/modules/event_replacements.md
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand All @@ -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!",
Expand Down
4 changes: 2 additions & 2 deletions content/client-server-api/modules/rich_replies.md
Original file line number Diff line number Diff line change
Expand Up @@ -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": {
Expand Down Expand Up @@ -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": {
Expand Down