Fix relative URLs when serving the specification with a custom baseURL (#1984)
This commit is contained in:
Kévin Commaille
GitHub
parent
b1f66d1b71
commit
bf8dee74eb
61 changed files with 101 additions and 92 deletions
|
|
@ -23,7 +23,7 @@ paths:
|
|||
Set some account data for the client. This config is only visible to the user
|
||||
that set the account data. The config will be available to clients through the
|
||||
top-level `account_data` field in the homeserver response to
|
||||
[/sync](#get_matrixclientv3sync).
|
||||
[/sync](/client-server-api/#get_matrixclientv3sync).
|
||||
operationId: setAccountData
|
||||
security:
|
||||
- accessTokenQuery: []
|
||||
|
|
@ -185,7 +185,7 @@ paths:
|
|||
description: |-
|
||||
Set some account data for the client on a given room. This config is only
|
||||
visible to the user that set the account data. The config will be delivered to
|
||||
clients in the per-room entries via [/sync](#get_matrixclientv3sync).
|
||||
clients in the per-room entries via [/sync](/client-server-api/#get_matrixclientv3sync).
|
||||
operationId: setAccountDataPerRoom
|
||||
security:
|
||||
- accessTokenQuery: []
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ paths:
|
|||
connection works.
|
||||
description: |-
|
||||
This API asks the homeserver to call the
|
||||
[`/_matrix/app/v1/ping`](#post_matrixappv1ping) endpoint on the
|
||||
[`/_matrix/app/v1/ping`](/application-service-api/#post_matrixappv1ping) endpoint on the
|
||||
application service to ensure that the homeserver can communicate
|
||||
with the application service.
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ paths:
|
|||
type: integer
|
||||
description: |-
|
||||
The duration in milliseconds that the
|
||||
[`/_matrix/app/v1/ping`](#post_matrixappv1ping)
|
||||
[`/_matrix/app/v1/ping`](/application-service-api/#post_matrixappv1ping)
|
||||
request took from the homeserver's point of view.
|
||||
required:
|
||||
- duration_ms
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ properties:
|
|||
The authentication type that the client is attempting to complete.
|
||||
May be omitted if `session` is given, and the client is reissuing a
|
||||
request which it believes has been completed out-of-band (for example,
|
||||
via the [fallback mechanism](#fallback)).
|
||||
via the [fallback mechanism](/client-server-api/#fallback)).
|
||||
type: string
|
||||
session:
|
||||
description: The value of the session key given by the homeserver.
|
||||
|
|
|
|||
|
|
@ -28,7 +28,8 @@ properties:
|
|||
items:
|
||||
type: string
|
||||
description: |-
|
||||
Chain of Curve25519 keys through which this session was forwarded, via [m.forwarded_room_key](#mforwarded_room_key) events.
|
||||
Chain of Curve25519 keys through which this session was forwarded, via [m.forwarded_room_key](/client-server-api/#mforwarded_room_key)
|
||||
events.
|
||||
sender_key:
|
||||
type: string
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -21,8 +21,8 @@ allOf:
|
|||
The format used to encode a Megolm session key for export.
|
||||
|
||||
This is similar to the format before encryption used for the session keys
|
||||
in [Server-side key backups](#server-side-key-backups) but adds the
|
||||
`room_id` and `session_id` fields.
|
||||
in [Server-side key backups](/client-server-api/#server-side-key-backups)
|
||||
but adds the `room_id` and `session_id` fields.
|
||||
properties:
|
||||
room_id:
|
||||
type: string
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ properties:
|
|||
type: boolean
|
||||
prev_batch:
|
||||
description: A token that can be supplied to the `from` parameter of the
|
||||
[`/rooms/<room_id>/messages`](#get_matrixclientv3roomsroomidmessages)
|
||||
[`/rooms/<room_id>/messages`](/client-server-api/#get_matrixclientv3roomsroomidmessages)
|
||||
endpoint in order to retrieve earlier events.
|
||||
|
||||
If no earlier events are available, this property may be omitted from
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ paths:
|
|||
description: |-
|
||||
A token which correlates to the start of `chunk`.
|
||||
Can be passed to
|
||||
[`/rooms/<room_id>/messages`](#get_matrixclientv3roomsroomidmessages)
|
||||
[`/rooms/<room_id>/messages`](/client-server-api/#get_matrixclientv3roomsroomidmessages)
|
||||
to retrieve earlier events.
|
||||
|
||||
If no earlier events are available, this property may be omitted from
|
||||
|
|
@ -183,7 +183,7 @@ paths:
|
|||
description: |-
|
||||
A token which correlates to the end of `chunk`.
|
||||
Can be passed to
|
||||
[`/rooms/<room_id>/messages`](#get_matrixclientv3roomsroomidmessages)
|
||||
[`/rooms/<room_id>/messages`](/client-server-api/#get_matrixclientv3roomsroomidmessages)
|
||||
to retrieve later events.
|
||||
chunk:
|
||||
type: array
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ paths:
|
|||
to ask other servers for a suitable event.
|
||||
|
||||
After calling this endpoint, clients can call
|
||||
[`/rooms/{roomId}/context/{eventId}`](#get_matrixclientv3roomsroomidcontexteventid)
|
||||
[`/rooms/{roomId}/context/{eventId}`](/client-server-api/#get_matrixclientv3roomsroomidcontexteventid)
|
||||
to obtain a pagination token to retrieve the events around the returned event.
|
||||
|
||||
The event returned by this endpoint could be an event that the client
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ paths:
|
|||
type: string
|
||||
description: |-
|
||||
A token which correlates to the start of `chunk`. Can be passed to
|
||||
[`/rooms/<room_id>/messages`](#get_matrixclientv3roomsroomidmessages)
|
||||
[`/rooms/<room_id>/messages`](/client-server-api/#get_matrixclientv3roomsroomidmessages)
|
||||
to retrieve earlier events.
|
||||
|
||||
If no earlier events are available, this property may be omitted from
|
||||
|
|
@ -63,7 +63,7 @@ paths:
|
|||
type: string
|
||||
description: |-
|
||||
A token which correlates to the end of `chunk`. Can be passed to
|
||||
[`/rooms/<room_id>/messages`](#get_matrixclientv3roomsroomidmessages)
|
||||
[`/rooms/<room_id>/messages`](/client-server-api/#get_matrixclientv3roomsroomidmessages)
|
||||
to retrieve later events.
|
||||
chunk:
|
||||
type: array
|
||||
|
|
|
|||
|
|
@ -26,8 +26,8 @@ paths:
|
|||
Where a child room is unknown to the local server, federation is used to fill in the details.
|
||||
The servers listed in the `via` array should be contacted to attempt to fill in missing rooms.
|
||||
|
||||
Only [`m.space.child`](#mspacechild) state events of the room are considered. Invalid child
|
||||
rooms and parent events are not covered by this endpoint.
|
||||
Only [`m.space.child`](/client-server-api/#mspacechild) state events of the room are considered.
|
||||
Invalid child rooms and parent events are not covered by this endpoint.
|
||||
operationId: getSpaceHierarchy
|
||||
security:
|
||||
- accessTokenQuery: []
|
||||
|
|
@ -44,8 +44,8 @@ paths:
|
|||
name: suggested_only
|
||||
description: |-
|
||||
Optional (default `false`) flag to indicate whether or not the server should only consider
|
||||
suggested rooms. Suggested rooms are annotated in their [`m.space.child`](#mspacechild) event
|
||||
contents.
|
||||
suggested rooms. Suggested rooms are annotated in their [`m.space.child`](/client-server-api/#mspacechild)
|
||||
event contents.
|
||||
example: true
|
||||
schema:
|
||||
type: boolean
|
||||
|
|
@ -103,8 +103,8 @@ paths:
|
|||
children_state:
|
||||
type: array
|
||||
description: |-
|
||||
The [`m.space.child`](#mspacechild) events of the space-room, represented
|
||||
as [Stripped State Events](#stripped-state) with an added `origin_server_ts` key.
|
||||
The [`m.space.child`](/client-server-api/#mspacechild) events of the space-room, represented
|
||||
as [Stripped State Events](/client-server-api/#stripped-state) with an added `origin_server_ts` key.
|
||||
|
||||
If the room is not a space-room, this should be empty.
|
||||
items:
|
||||
|
|
|
|||
|
|
@ -223,8 +223,8 @@ paths:
|
|||
The new ephemeral events in the room (events that
|
||||
aren't recorded in the timeline or state of the
|
||||
room). In this version of the spec, these are
|
||||
[typing notification](#typing-notifications) and
|
||||
[read receipt](#receipts) events.
|
||||
[typing notification](/client-server-api/#typing-notifications)
|
||||
and [read receipt](/client-server-api/#receipts) events.
|
||||
allOf:
|
||||
- $ref: definitions/event_batch.yaml
|
||||
account_data:
|
||||
|
|
@ -245,7 +245,7 @@ paths:
|
|||
|
||||
If `unread_thread_notifications` was specified as `true` on the `RoomEventFilter`,
|
||||
these counts will only be for the main timeline rather than all events in the room.
|
||||
See the [threading module](#threading) for more information.
|
||||
See the [threading module](/client-server-api/#threading) for more information.
|
||||
x-changedInMatrixVersion:
|
||||
"1.4": |
|
||||
Updated to reflect behaviour of having `unread_thread_notifications` as `true` in
|
||||
|
|
@ -265,8 +265,8 @@ paths:
|
|||
type: object
|
||||
description: |-
|
||||
If `unread_thread_notifications` was specified as `true` on the `RoomEventFilter`,
|
||||
the notification counts for each [thread](#threading) in this room. The object is
|
||||
keyed by thread root ID, with values matching `unread_notifications`.
|
||||
the notification counts for each [thread](/client-server-api/#threading) in this room.
|
||||
The object is keyed by thread root ID, with values matching `unread_notifications`.
|
||||
|
||||
If a thread does not have any notifications it can be omitted from this object. If
|
||||
no threads have notification counts, this whole object can be omitted.
|
||||
|
|
@ -302,12 +302,13 @@ paths:
|
|||
title: InviteState
|
||||
type: object
|
||||
description: |-
|
||||
The [stripped state](#stripped-state) of a room that the user has been invited
|
||||
to.
|
||||
The [stripped state](/client-server-api/#stripped-state) of a room that the user has
|
||||
been invited to.
|
||||
properties:
|
||||
events:
|
||||
description: The [stripped state events](#stripped-state) that form the invite
|
||||
state.
|
||||
description: |-
|
||||
The [stripped state events](/client-server-api/#stripped-state) that form the
|
||||
invite state.
|
||||
items:
|
||||
$ref: ../../event-schemas/schema/core-event-schema/stripped_state.yaml
|
||||
type: array
|
||||
|
|
@ -325,12 +326,14 @@ paths:
|
|||
knock_state:
|
||||
title: KnockState
|
||||
type: object
|
||||
description: The [stripped state](#stripped-state) of a room that the user has
|
||||
description: |-
|
||||
The [stripped state](/client-server-api/#stripped-state) of a room that the user has
|
||||
knocked upon.
|
||||
properties:
|
||||
events:
|
||||
description: The [stripped state events](#stripped-state) that form the knock
|
||||
state.
|
||||
description: |-
|
||||
The [stripped state events](/client-server-api/#stripped-state) that form the
|
||||
knock state.
|
||||
items:
|
||||
$ref: ../../event-schemas/schema/core-event-schema/stripped_state.yaml
|
||||
type: array
|
||||
|
|
|
|||
|
|
@ -57,9 +57,9 @@ paths:
|
|||
x-addedInMatrixVersion: "1.2"
|
||||
type: boolean
|
||||
description: |-
|
||||
When `true`, the user is a [Guest User](#guest-access). When
|
||||
not present or `false`, the user is presumed to be a non-guest
|
||||
user.
|
||||
When `true`, the user is a [Guest User](/client-server-api/#guest-access).
|
||||
When not present or `false`, the user is presumed to be a
|
||||
non-guest user.
|
||||
examples:
|
||||
response:
|
||||
value: {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue