From 31e575de0231614cb8979d0621420a3826b80f5c Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Fri, 7 Jun 2024 11:58:04 +0100 Subject: [PATCH] fix link --- .../definitions/client_event_without_room_id.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/data/api/client-server/definitions/client_event_without_room_id.yaml b/data/api/client-server/definitions/client_event_without_room_id.yaml index c1061029..b1242004 100644 --- a/data/api/client-server/definitions/client_event_without_room_id.yaml +++ b/data/api/client-server/definitions/client_event_without_room_id.yaml @@ -118,10 +118,11 @@ properties: The room membership of the user making the request, at the time of the event. This property is the value of the `membership` property of the - requesting user's [`m.room.member`](#mroommember) state at the point - of the event, including any changes caused by the event. If the user - had yet to join the room at the time of the event (i.e, they have no - `m.room.member` state), this property is set to `leave`. + requesting user's [`m.room.member`](/client-server-api#mroommember) + state at the point of the event, including any changes caused by the + event. If the user had yet to join the room at the time of the event + (i.e, they have no `m.room.member` state), this property is set to + `leave`. It is recommended that homeservers SHOULD populate this property wherever practical, but they MAY omit it if necessary (for example,