From 8a050aebc0e085455ff99aad663d39e1efecddae Mon Sep 17 00:00:00 2001 From: Mark Haines Date: Mon, 15 Feb 2016 17:17:58 +0000 Subject: [PATCH] Add a note to the docs for before and after to make it clear that they cannot be used with the predefined rules --- api/client-server/pushrules.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/api/client-server/pushrules.yaml b/api/client-server/pushrules.yaml index 07bd6bdb..2aba7bd9 100644 --- a/api/client-server/pushrules.yaml +++ b/api/client-server/pushrules.yaml @@ -380,7 +380,8 @@ paths: x-example: someRuleId description: |- Use 'before' with a ``rule_id`` as its value to make the new rule the - next-most important rule with respect to the given rule. + next-most important rule with respect to the given user defined rule. + It is not possible to add a rule relative to a predefined server rule. - in: query type: string name: after @@ -388,7 +389,8 @@ paths: x-example: anotherRuleId description: |- This makes the new rule the next-less important rule relative to the - given rule. + given user defined rule. It is not possible to add a rule relative + to a predefined server rule. - in: body name: pushrule description: |-