Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

"default" field in PushRule omitted for user-defined push rules #6636

@Karlinde

Description

@Karlinde

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 default field.

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
  • Platform: Docker in Ubuntu running on a VPS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-Spec-Complianceplaces where synapse does not conform to the specz-bug(Deprecated Label)z-p2(Deprecated Label)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions