Skip to content

Commit

Permalink
Clarify that dont_notify and coalesce MUST be gracefully ignored (#1890)
Browse files Browse the repository at this point in the history
  • Loading branch information
Johennes committed Jul 10, 2024
1 parent 2261c03 commit e4589bb
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 4 deletions.
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1890.clarification
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that the deprecated `dont_notify` and `coalesce` push rule actions MUST be ignored, not rejected.
10 changes: 6 additions & 4 deletions content/client-server-api/modules/push.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
`{ "set_tweak": "sound", "value": "default" }`.

{{% boxes/note %}}
###### Historical Actions

Older versions of the Matrix specification included the `dont_notify` and
`coalesce` actions. These should both be considered no-ops (ignored, not
rejected) if received from a client.
{{% /boxes/note %}}
`coalesce` actions. Clients and homeservers MUST ignore these actions, for
instance, by stripping them from actions arrays they encounter. This means,
for example, that a rule with `["dont_notify"]` actions MUST be equivalent
to a rule with an empty actions array.

##### Conditions

Expand Down

0 comments on commit e4589bb

Please sign in to comment.