From f9472bae411e8db020247eb7394d7bd42fe50d5a Mon Sep 17 00:00:00 2001
From: Travis Ralston <travpc@gmail.com>
Date: Wed, 29 May 2019 16:27:16 -0600
Subject: [PATCH] Change reference for definition of push rule condition kinds

Fixes https://github.com/matrix-org/matrix-doc/issues/1970
---
 api/client-server/definitions/push_condition.yaml    | 12 ++++++++----
 .../client_server/newsfragments/2052.clarification   |  1 +
 2 files changed, 9 insertions(+), 4 deletions(-)
 create mode 100644 changelogs/client_server/newsfragments/2052.clarification

diff --git a/api/client-server/definitions/push_condition.yaml b/api/client-server/definitions/push_condition.yaml
index 796a51f47..8752274e2 100644
--- a/api/client-server/definitions/push_condition.yaml
+++ b/api/client-server/definitions/push_condition.yaml
@@ -16,16 +16,20 @@ title: PushCondition
 type: object
 properties:
   kind:
-    enum:
-    - event_match
-    - contains_display_name
-    - room_member_count
     type: string
+    description: |-
+      The kind of condition to apply. See `conditions <#conditions>`_ for
+      more information on the allowed kinds and how they work.
   key:
     type: string
     description: |-
       Required for ``event_match`` conditions. The dot-separated field of the
       event to match.
+
+      Required for ``sender_notification_permission`` conditions. The field in
+      the power level event the user needs a minimum power level for. Fields
+      must be specified under the ``notifications`` property in the power level
+      event's ``content``.
     x-example: content.body
   pattern:
     type: string
diff --git a/changelogs/client_server/newsfragments/2052.clarification b/changelogs/client_server/newsfragments/2052.clarification
new file mode 100644
index 000000000..95bdc9282
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2052.clarification
@@ -0,0 +1 @@
+Clarify which push rule condition kinds exist.