Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-14 01:53:43 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

The event *format* changes, not the version

Browse source
This commit is contained in:
Travis Ralston 2019-02-01 13:19:24 -07:00
parent 890fb1a019
commit 82bed06d3f
9 changed files with 19 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
api/server-server/definitions/invite_event.yaml
View file

@ -14,7 +14,7 @@
type: object
title: Invite Event
description: |-
An invite event. Note that events have a different version depending on the
An invite event. Note that events have a different format depending on the
room version - check the `room version specification`_ for precise event formats.
allOf:
- type: object

2
api/server-server/definitions/transaction.yaml
View file

@ -33,7 +33,7 @@ properties:
type: array
description: |-
List of persistent updates to rooms. Must not include more than 50 PDUs. Note that
events have a different version depending on the room version - check the
events have a different format depending on the room version - check the
`room version specification`_ for precise event formats.
items:
type: object

6
api/server-server/event_auth.yaml
View file

@ -59,7 +59,7 @@ paths:
description: |-
The full set of authorization events that make up the state of
the room, and their authorization events, recursively. Note that
events have a different version depending on the room version -
events have a different format depending on the room version -
check the `room version specification`_ for precise event formats.
items:
type: object
@ -109,7 +109,7 @@ paths:
type: array
description: |-
The auth chain (the "remote auth"). Note that events have a different
version depending on the room version - check the `room version specification`_
format depending on the room version - check the `room version specification`_
for precise event formats.
items:
type: object
@ -162,7 +162,7 @@ paths:
description: |-
The auth chain the receiver has, and used to determine the auth
chain differences (the "local auth"). Note that events have a different
version depending on the room version - check the `room version specification`_
format depending on the room version - check the `room version specification`_
for precise event formats.
items:
type: object

4
api/server-server/events.yaml
View file

@ -60,7 +60,7 @@ paths:
description: |-
The full set of authorization events that make up the state
of the room, and their authorization events, recursively. Note that
events have a different version depending on the room version -
events have a different format depending on the room version -
check the `room version specification`_ for precise event formats.
items:
type: object
@ -76,7 +76,7 @@ paths:
type: array
description: |-
The fully resolved state of the room at the given event. Note that
events have a different version depending on the room version -
events have a different format depending on the room version -
check the `room version specification`_ for precise event formats.
items:
type: object

4
api/server-server/invites-v1.yaml
View file

@ -39,7 +39,7 @@ paths:
which receive a v1 invite request must assume that the room version is either ``"1"``
or ``"2"``.
Note that events have a different version depending on the room version - check the
Note that events have a different format depending on the room version - check the
`room version specification`_ for precise event formats. **The request and response
bodies here describe the common event fields in more detail and may be missing other
required fields for a PDU.**
@ -151,7 +151,7 @@ paths:
200:
description: |-
The event with the invited server's signature added. All other fields of the events
should remain untouched. Note that events have a different version depending on the
should remain untouched. Note that events have a different format depending on the
room version - check the `room version specification`_ for precise event formats.
schema:
type: array

4
api/server-server/invites-v2.yaml
View file

@ -43,7 +43,7 @@ paths:
which receive a 400 or 404 response to this endpoint should retry using the v1
API as the server may be older, if the room version is "1" or "2".
Note that events have a different version depending on the room version - check the
Note that events have a different format depending on the room version - check the
`room version specification`_ for precise event formats. **The request and response
bodies here describe the common event fields in more detail and may be missing other
required fields for a PDU.**
@ -154,7 +154,7 @@ paths:
200:
description: |-
The event with the invited server's signature added. All other fields of the events
should remain untouched. Note that events have a different version depending on the
should remain untouched. Note that events have a different format depending on the
room version - check the `room version specification`_ for precise event formats.
schema:
type: object

8
api/server-server/joins.yaml
View file

@ -62,7 +62,7 @@ paths:
200:
description: |-
A template to be used for the rest of the `Joining Rooms`_ handshake. Note that
events have a different version depending on the room version - check the
events have a different format depending on the room version - check the
`room version specification`_ for precise event formats. **The response body
here describes the common event fields in more detail and may be missing other
required fields for a PDU.**
@ -77,7 +77,7 @@ paths:
example: "2"
event:
description: |-
An unsigned template event. Note that events have a different version
An unsigned template event. Note that events have a different format
depending on the room version - check the `room version specification`_
for precise event formats.
type: object
@ -165,7 +165,7 @@ paths:
description: |-
Submits a signed join event to the resident server for it
to accept it into the room's graph. Note that events have
a different version depending on the room version - check
a different format depending on the room version - check
the `room version specification`_ for precise event formats.
**The request and response body here describes the common
event fields in more detail and may be missing other required
@ -265,7 +265,7 @@ paths:
auth_chain:
type: array
description: |-
The auth chain. Note that events have a different version depending on
The auth chain. Note that events have a different format depending on
the room version - check the `room version specification`_ for precise
event formats.
items:

6
api/server-server/leaving.yaml
View file

@ -53,7 +53,7 @@ paths:
200:
description: |-
A template to be used to call ``/send_leave``. Note that
events have a different version depending on the room version - check the
events have a different format depending on the room version - check the
`room version specification`_ for precise event formats. **The response body
here describes the common event fields in more detail and may be missing other
required fields for a PDU.**
@ -69,7 +69,7 @@ paths:
example: "2"
event:
description: |-
An unsigned template event. Note that events have a different version
An unsigned template event. Note that events have a different format
depending on the room version - check the `room version specification`_
for precise event formats.
type: object
@ -144,7 +144,7 @@ paths:
description: |-
Submits a signed leave event to the resident server for it
to accept it into the room's graph. Note that events have
a different version depending on the room version - check
a different format depending on the room version - check
the `room version specification`_ for precise event formats.
**The request and response body here describes the common
event fields in more detail and may be missing other required

2
api/server-server/transactions.yaml
View file

@ -38,7 +38,7 @@ paths:
The sending server must wait and retry for a 200 OK response before sending a
transaction with a different ``txnId`` to the receiving server.
Note that events have a different version depending on the room version - check
Note that events have a different format depending on the room version - check
the `room version specification`_ for precise event formats.
operationId: sendTransaction
security: