Clarify that usage of event_id_only is not mandatory (#2255)
Some checks failed
Spec / 🔎 Validate OpenAPI specifications (push) Has been cancelled
Spec / 🔎 Check Event schema examples (push) Has been cancelled
Spec / 🔎 Check OpenAPI definitions examples (push) Has been cancelled
Spec / 🔎 Check JSON Schemas inline examples (push) Has been cancelled
Spec / ⚙️ Calculate baseURL for later jobs (push) Has been cancelled
Spec / 📢 Run towncrier for changelog (push) Has been cancelled
Spell Check / Spell Check with Typos (push) Has been cancelled
Spec / 🐍 Build OpenAPI definitions (push) Has been cancelled
Spec / 📖 Build the spec (push) Has been cancelled
Spec / 🔎 Validate generated HTML (push) Has been cancelled
Spec / 📖 Build the historical backup spec (push) Has been cancelled

Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
This commit is contained in:
Johannes Marbach 2025-12-01 18:41:42 +01:00 committed by GitHub
parent b1fd2af72c
commit d28e05af87
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 9 additions and 5 deletions

View file

@ -0,0 +1 @@
Usage of the `event_id_only` format for push notifications is not mandatory.

View file

@ -230,11 +230,14 @@ paths:
format:
type: string
description: |-
The format to send notifications in to Push Gateways if the
`kind` is `http`. The details about what fields the
homeserver should send to the push gateway are defined in the
[Push Gateway Specification](/push-gateway-api/). Currently the only format
available is 'event_id_only'.
The format in which to send notifications to the push gateway
if the `kind` is `http`. The details about what fields the
homeserver should include are defined in the
[Push Gateway Specification](/push-gateway-api/). If omitted,
the server is expected to populate all of the event-related fields
specified in [`/_matrix/push/v1/notify`](/push-gateway-api/#post_matrixpushv1notify).
enum:
- "event_id_only"
append:
type: boolean
description: |-