Describe how get_missing_events actually works

The original text wasn't far off, except for being wrong about what the fields actually do. This commit also adds a bit of clarity for how the server is expected to behave.
This commit is contained in:
Travis Ralston 2018-08-08 08:39:59 -06:00
parent 521dcdd5d5
commit 721be47eb1

View file

@ -81,8 +81,9 @@ paths:
post: post:
summary: Retrieves events that the sender is missing summary: Retrieves events that the sender is missing
description: |- description: |-
Retrieves the previous events that the sender is missing for a given set of Retrieves previous events that the sender is missing. This is done by doing a breadth-first
events. walk of the ``prev_events`` for the ``latest_events``, ignoring any events in ``earliest_events``
and stopping at the ``limit``.
operationId: getMissingPreviousEvents operationId: getMissingPreviousEvents
parameters: parameters:
- in: path - in: path
@ -107,15 +108,14 @@ paths:
earliest_events: earliest_events:
type: array type: array
description: |- description: |-
The events the sender is missing. The response will only contain events The latest events that the sender already has. These are skipped when retrieving
that didn't happen before these events. the previous events of ``latest_events``.
items: items:
type: string type: string
example: ["$missing_event:domain.com"] example: ["$missing_event:domain.com"]
latest_events: latest_events:
type: array type: array
description: |- description: The events to retrieve the previous events for.
The events that the sender has, but does not have previous events for.
items: items:
type: string type: string
example: ["$event_that_has_the_missing_event_as_a_previous_event:domain.com"] example: ["$event_that_has_the_missing_event_as_a_previous_event:domain.com"]
@ -123,9 +123,8 @@ paths:
responses: responses:
200: 200:
description: |- description: |-
The events that happened after the ``earliest_events`` which are also previous The previous events for ``latest_events``, excluding any ``earliest_events``, up to the
to the ``latest_events`` and have the minimum depth specified. Does not include provided ``limit``.
any of the events in the request.
schema: schema:
type: object type: object
properties: properties: