Clarify that dont_notify and coalesce MUST be gracefully ignored (#1890)
This commit is contained in:
parent
2261c03bcd
commit
e4589bbc8a
2 changed files with 7 additions and 4 deletions
|
@ -0,0 +1 @@
|
||||||
|
Clarify that the deprecated `dont_notify` and `coalesce` push rule actions MUST be ignored, not rejected.
|
|
@ -184,11 +184,13 @@ they are represented as a dictionary with a key equal to their name and
|
||||||
other keys as their parameters, e.g.
|
other keys as their parameters, e.g.
|
||||||
`{ "set_tweak": "sound", "value": "default" }`.
|
`{ "set_tweak": "sound", "value": "default" }`.
|
||||||
|
|
||||||
{{% boxes/note %}}
|
###### Historical Actions
|
||||||
|
|
||||||
Older versions of the Matrix specification included the `dont_notify` and
|
Older versions of the Matrix specification included the `dont_notify` and
|
||||||
`coalesce` actions. These should both be considered no-ops (ignored, not
|
`coalesce` actions. Clients and homeservers MUST ignore these actions, for
|
||||||
rejected) if received from a client.
|
instance, by stripping them from actions arrays they encounter. This means,
|
||||||
{{% /boxes/note %}}
|
for example, that a rule with `["dont_notify"]` actions MUST be equivalent
|
||||||
|
to a rule with an empty actions array.
|
||||||
|
|
||||||
##### Conditions
|
##### Conditions
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue