This repository was archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
"default" field in PushRule omitted for user-defined push rules #6636
Copy link
Copy link
Closed
Labels
A-Spec-Complianceplaces where synapse does not conform to the specplaces where synapse does not conform to the specz-bug(Deprecated Label)(Deprecated Label)z-p2(Deprecated Label)(Deprecated Label)
Description
Description
The spec states that for push rules returned from the server, the field default is required. Synapse however seems to omit this field for user-defined rules, leading to deserialization failures for a spec-compliant client that expects it when fetching push rules.
Steps to reproduce
- Push a user-defined push rule to synapse using
PUT /_matrix/client/r0/pushrules/{scope}/{kind}/{ruleId}. - Fetch all push rules using
GET /_matrix/client/r0/pushrules/. - Find the newly created rule in the returned ruleset. It doesn't have a
defaultfield.
Since the spec states that the default field is required, I did not expect the server to be allowed to omit it.
Version information
- Homeserver: private, not federating
-
Version: 1.7.3
-
Install method: Ansible playbook from https://github.com/spantaleev/matrix-docker-ansible-deploy
- Platform: Docker in Ubuntu running on a VPS.
Metadata
Metadata
Assignees
Labels
A-Spec-Complianceplaces where synapse does not conform to the specplaces where synapse does not conform to the specz-bug(Deprecated Label)(Deprecated Label)z-p2(Deprecated Label)(Deprecated Label)